Re: alias target not local?

From: Zbynek Winkler (zwin_at_[hidden])
Date: 2003-12-09 04:28:27

Vladimir Prus wrote:

> Zbynek Winkler wrote:
> 
>>I've attempted to create a minimal example showing this (see
>>attachment). This really shows all the symptomps as described (creates
>>link problem when two "_main"s are defined). But during the
>>"minimization" I've found an error (in mcl/Jamfile there is "/number"
>>instead of "/number//number"). However bjam did not report anything.
>>When attempting to remove some more lines (regarding the system library
>>cppunit) I get some error that I am not sure what to think of. Could you
>>tell me what the problem really is here?
> 
> 
> I don't think there's any bug. The reference "/number" is allows, and means 
> "project called /number". IOW, when "mcl/test" is build it also builds *all* 
> targets from "/number", including "number_test.cpp" and uses those targets as 
> sources. So, "number_test.cpp" is compiled, too, giving multiple declaration 
> error.

The example as sent did not give me any errors except for linking when 
the compiler says that there are multiple _main defined.

> I think changing /number to /number//number should fix this. Let me know if 
> you continue to have problems.

Yes that fixed it. What I was curious about is why it didn't give any 
errors/warnings.

Zbynek

-- 
http://zw.matfyz.cz/ http://robotika.cz/
Faculty of Mathematics and Physics, Charles University, Prague, Czech 
Republic