[Clam-devel] IMPORTANT: more changes to build system

Xavier Amatriain xavier at create.ucsb.edu
Fri Jun 1 00:40:44 PDT 2007


Yes, that option has no effect and I can't still compile from Eclipse.

This is the command line output from Eclipse everytime I call
Scons->build from the plug-in:

scons -u -Q platform=default configuration=release
force_avoid_configure=1 . 
scons: Entering directory `/home/xavier/Sandbox/trunk/CLAM'
Version:  1.0.1
Package version:  1.0.1~svn10158
############################################
### CLAM GLOBAL DEPENDENCIES CHECKING    ###
############################################
#########################################
### CLAM CORE DEPENDENCIES CHECKING   ###
#########################################
path of
app: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
###############################################
### CLAM PROCESSING DEPENDENCIES CHECKING   ###
###############################################
############################################
### CLAM AUDIOIO DEPENDENCIES CHECKING   ###
############################################
Finished. Invoke 'scons' now.


On Fri, 2007-06-01 at 09:19 +0200, Pau Arumi wrote:
> Xavier Amatriain wrote:
> > A brief update on this issue: this now seems to work with NetworkEditor
> > and possibly other CLAM apps but NOT when calling scons for building the
> > CLAM libs!
> 
> you mean the new "scons force_avoid_configure=1" option, right?
> it have nothing to do with clam apps. it's only for libs.
> 
> please be specific. what is the problem?
> 
> pau
> 
> 
> > 
> > On Mon, 2007-05-28 at 11:37 +0200, Pau Arumi wrote:
> >> Ok, now I understand the problem: the scons eclipse plugin extract
> >> (parses?) the options from the SConstruct file, gives the user an
> >> interface to change its values, and passes all of them on each
> >> scons invocation.
> >>
> >> It seems to me that the plugin writers don't like the options cache
> >> feature that scons have already, a pity.
> >>
> >> To overcome this problem I've added a new option to SConstruct. Its
> >> meaning should be clear. Tell me if it is not.
> >>
> >>  From scons --help:
> >>
> >> force_avoid_configure: Avoid configure phase. Useful for Eclipse 
> >> scons plugin. Enable it only if you know what you are doing (yes|no)
> >>      default: no
> >>      actual: 0
> >>
> >> Note that there is a difference between doing
> >> "scons configure" and "scons force_avoid_configure=1"
> >> the first is not a scons option, thus not accessible from the
> >> eclipse plugin. And the first is not cached or stored (in
> >> option.cache) while the second is.
> >>
> >> Pau
> >>
> >> En/na Xavier Amatriain ha escrit:
> >>> Uhm... let me try again: Eclipse CANNOT call just scons... period. It 
> >>> always calls it with a configuration.
> >>> Yes, I can call 'scons' from the command line, outside Eclipse but...
> >>>
> >>> this is a big issue because one of the points in Eclipse is that it 
> >>> automatically builds and indexes
> >>> things as you work.
> >>>
> >>> David García Garzón wrote:
> >>>> As a summary:
> >>>>
> >>>> - You must call once 'scons configure' with any parameters.
> >>>> - Parameters are catched on the options.cache file and configuration 
> >>>> dependant files are generated.
> >>>> - Then you call simply 'scons' and that's all.
> >>>> - Doing 'scons parameter=value' is equivalent to do an 'scons 
> >>>> configure parameter=value'
> >>>>
> >>>> So do the configuration step by hand (if eclipse doesnt support 
> >>>> specifying such step) and then just 'scons' or 'scons install'.
> >>>>
> >>>> David.
> >>>>
> >>>>
> >>>> On Thursday 24 May 2007 17:09:06 Pau Arumi wrote:
> >>>>  
> >>>>> Xavier Amatriain wrote:
> >>>>>    
> >>>>>> I think you understood it the other way around: what Eclipse can't 
> >>>>>> do is
> >>>>>> call scons without arguments.
> >>>>>> Calling configure from outside does not help because every time 
> >>>>>> scons is
> >>>>>> called with arguments configure
> >>>>>> is called again.
> >>>>>>       
> >>>>> but you *can* call scons without arguments, can't you?
> >>>>> then where is the problem?
> >>>>>
> >>>>> p
> >>>>>
> >>>>>    
> >>>>>> What I would need is for scons without arguments to be called
> >>>>>> automatically after the configure step
> >>>>>> (if this is going to be enforced).
> >>>>>>
> >>>>>> David García Garzón wrote:
> >>>>>>      
> >>>>>>> On Thursday 24 May 2007 12:02:08 Pau Arumi wrote:
> >>>>>>>        
> >>>>>>>> Xavier Amatriain wrote:
> >>>>>>>>          
> >>>>>>>>> On Wed, 2007-05-23 at 09:14 +0200, Pau Arumi wrote:
> >>>>>>>>>            
> >>>>>>>>>> this issue probably shows up now just because now on every "scons
> >>>>>>>>>> option=value" invocaton, the configure step is automatically
> >>>>>>>>>> called (which, btw, i a *very* convenient change).
> >>>>>>>>>>               
> >>>>>>>>> Unfortunately I just realized that this harmless change just broke
> >>>>>>>>> compatibility of CLAM with Eclipse (just when I was starting to get
> >>>>>>>>> the hang of it :-( ). Turns out that there is no way to call scons
> >>>>>>>>> from the Eclipse plugin without the platform and configuration
> >>>>>>>>> options. Therefore
> >>>>>>>>> no matter what you do you are always invoking the configure step and
> >>>>>>>>> nothing else.
> >>>>>>>>>
> >>>>>>>>> Isn't there a way that, while keeping the call to configure if
> >>>>>>>>> necessary, also forces the call to "scons" immediately afterwords?
> >>>>>>>>>             
> >>>>>>>> possible is everything ;)
> >>>>>>>> but... the "call to configure only if necessary" is the hard part
> >>>>>>>> to implement since it involves comparing the given and cached
> >>>>>>>> options.
> >>>>>>>>
> >>>>>>>> i'd rather change the eclipse/scons workflow, if possible.
> >>>>>>>> wouldn't it be as simple as editing the options.cache by hand and
> >>>>>>>> then call "scons" without args from the ide?
> >>>>>>>>           
> >>>>>>> In fact you should call externally 'scons configure' as it also
> >>>>>>> generates the pkg-config files and the flags.conf file. Is weird that
> >>>>>>> eclipse can not configure a 'configuration' step.
> >> _______________________________________________
> >> Clam-devel mailing list
> >> Clam-devel at llistes.projectes.lafarga.org
> >> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel
> > 
> > 
> > _______________________________________________
> > Clam-devel mailing list
> > Clam-devel at llistes.projectes.lafarga.org
> > https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel
> 
> 
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel





More information about the clam-devel mailing list