Boost logo

Boost-Build :

From: elesende (elesende_at_[hidden])
Date: 2004-06-23 19:48:32

Thank you so much for your help. The java module is now much closer
to completion. :)

Its working pretty good. I have one problem thou, that Im unable to
solve by myself. Here's the deal:

I have two sources, lets say:

They both get builded at $(build-dir)/bin/jdk/debug (for example).
So after updating this sources, I get the following file-targets:


Which is perfectly fine and is exactly what I wanted. Now the
problem is at the archiver. The JAR tool. The JAR tool should be
called like this:

jar -c $(build-dir)/bin/jdk/debug/somejar.jar -C $(build-
dir)/bin/jdk/debug com/pack1/pack2/Vector.class

I added a build-dir feature and binded it at the action so I can do

jar -c $(<) -C $(BUILDDIR) $(>)

The thing is that $(>) gets expanded to $(build-
dir)/bin/jdk/debug/com/pack1/pack2/Vector.class and $(build-
dir)/bin/jdk/debug/com/pack1/pack2/Quaternion.class which is not a
relative path to $(build-dir)/bin/jdk/debug so it doesnt work. If I
don't do it this way I get the wrong directory structure inside the
jar file which is bad also.

Ive been hitting my head against the wall with this. I tried to
create a new derivate of file-target, so I overload the actualize-
location rule, but this will affect the compilation and I don't want
that. Is there a way AFTER it compiled the sources, reset the LOCATE
on $(target)?

Any other ideas?

BTW: My email is elesende_at_[hidden], if you can send there
other contact information like ICQ# or IRC chat room, Ill be more
than grateful.

Thanks in advance,


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at