Re: [jamboost] Targets in command line( Was: I'm back!)

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-10-18 10:13:19

David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> 
> 
>>David Abrahams wrote:
>>
>>Good. Probably, when all of Boost is buildable (I haven't tried
>>Python, and there might be some problems with threads), you can try
>>to implement this? That's a good change to dig into as yet unknown
>>parts of code.
> 
> 
> I'll try.

Great. BTW, I hope to release Milestone2 (i.e. to build all of Boost) in 
the beginning of next week. I've a question -- what will we do with 
Boost.Python, which depends on Python includes location. We might add 
some auto-sensing using GLOB, so that it works now. Later, we'll take 
care of it when implementing toolset interface.

>>>>>Yeah, it is... though I think we ought to consider supporting such
>>>>>things as:
>>>>>
>>>>> bjam --compile=foo/bar/baz.cpp
>>>>> bjam --preprocess=foo/bar.cpp
>>>>>
>>>>>
>>>>>and probably also:
>>>>>
>>>>> bjam --recompile=foo/bar/baz.cpp # no dependency checking!
>>>>
>>>>Well, the last thing is just "-a" switch to bjam. About "--compile"... 
>>>>is it in any way different from
>>>>
>>>> bjam foo/bar/baz.o
>>>
>>>
>>>It's a push -vs- pull thing. When I "just want to compile this file" I
>>>don't want to have to think about what kind of target it generates or
>>>how to name it.
>>
>>I get you. However, the only semantic I can think of is:
>>
>> execute only the actions which are compiles, and which uses
>> foo/bar/baz.cpp
> 
> 
> What about just, "execute all actions which have foo/bar/baz.cpp as an
> immediate source"?

Hmm.... then, why "--compile" in command line?!

>>You know, this is similar to my old idea to run only selected actions, 
>>which are not universaly available. For example, using a modification of 
>>your proposed syntax:
>>
>> bjam --action=bison.bison
>>
>>Would construct dependency graph for "." and run only "bison.bison" 
>>actions. Back you what you've proposed, we can allow
>>
>> bjam --action=*.compile
>>
>>to run all compile action and some variation of this syntax for compile 
>>only one source file:
>>
>> bjam --action=*.compile%foo/bar/baz.cpp
> 
> 
> Hmm, it's kind of ugly. Let's make this a low priority until we think
> of a nice way to express it, OK?

I'm not happy about this syntax either, but the functionality is 
something I'd like to get in 2.0. Let's revisit it later.

- Volodya