[openbeos-build-team] Re: Dependency confusion

  • From: "Erik Jaesler" <erik@xxxxxxxxxxxxxx>
  • To: openbeos-build-team@xxxxxxxxxxxxx
  • Date: Wed, 10 Jul 2002 23:22:36 -0700

One more thing.  I have noticed (after doing a build from root) that the 
DriveSetup, Fonts, and VirtualMemory prefs apps all have the same icon 
(VirtualMemory's icon).  This struck me as a bit weird because I build 
them earlier -- from their own directories -- and they didn't have the 
same icon then.  I dug a bit deeper and found that each app calls its 
resource file Resource.rsrc.  Apparently jam is using the last one found 
for all of them.  Is there some way to fix this, or will we be forced to 
rename the files?  It's not such a big deal in this case, but I'm a bit 
concerned as far as problems with same-name source files is concerned.


>> I'm a bit confused as to why, when I run jam from 
>> current/src/tests/kits/app/, I get complaints about "don't know how 
>> to 
>> make libcppunit.so".  I was under the impression that jam built the 
>> entire dependency tree regardless of where in the tree you were 
>> building.  That being the case, why doesn't jam "know how to make 
>> libcppunit.so" when it's clearly in the tree?
>Your impression is unfortunately incorrect. The current Jam system can 
>only build targets in the current directory or subdirectories. I 
>critized this behavior as a side note on this list earlier. It can be 
>fixed, but not without changing Jambase.
>Anyway, it is not too bad, as you can pass the target you want to build 

>to the jam command invoked in the tree's root directory.
>CU, Ingo

Necessity is the plea for every infringement of human freedom. It is the 
argument of tyrants; it is the creed of slaves.
        -William Pitt, British prime-minister (1759-1806)

Other related posts: