Re: [jamboost] M4: Several minor glitches

From: Jürgen Hunold (hunold+lists.Boost_at_[hidden])
Date: 2003-07-07 01:57:56

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Volodya !

On Wednesday 02 July 2003 15:05, Vladimir Prus wrote:

> Hi Jürgen! I almost started to wander where you've disappeared :-)
> Welcome back, and sorry for delayed reply.

Sorry, I ran into an unannounced meeting and unforeseen problems
upgrading mit W2k Box to VC 7.1 last week. But now I should be able to
check my mail regularly.

> It's probably possible to allow project-root.jam to change type of .c
> files to C++, though it looks like a bad solution: we need this only
> for a single project, not globally.

Do you know how ?

> > 2. Platform dependent dependencies.
> contain code covering this.
>
> I think you're the third person who encounters this same issue, so it
> should be addressed now.

> "I'd like to use feature such-and-such, if it's already valid,
> it's OK, otherwise, please make it valid".
>
> Something like:
>
> feature.ensure-valid <os>LINUX <os>NT ;
>
> What would you say about this approach.

Sounds good. This would work for every feature, like <toolset>, right ?
And bjam would catch typos when I the do <os>LINUS or so.
Where would I put this ? I guess boost-build.jam ?
+1 from my side.

> > 3. STLport.
> >
> > Working great, but find a diff attached which eliminates annoying
> >
> > warning: target id '@/stlport/stlport uses deprecated syntax,
> > warning: which may be removed in a future version.
> > warning: reference is made from project at 'RailSys/simu'
>
> I've made the correction. Thanks!

Could you please fix qt.jam. It also contains old syntax. Thanx !

> > I wonder if bjam could support static linking of STLport on Win32
> > using
> >
> > <define>_STLP_USE_STATIC_LIB
> > <define>_RTLDLL
> >
> > somehow.
> > This results in linking against static lib, using system runtime.
> > It uses special stlport lib with _staticx extension, build by
> > stlport make target "staticx". It is quite useful, because I dont
> > have to deliver STLport .dll to my customers.
>
> So, to use stlport on windows with <link>static you'd have to
> - use different name of library
> - add those two defines ?

Yes. You got it.

> Yep, I think it is possible. Probably, you could try adding this
> feature yourself, since I don't have static stlport readily
> available? The name is computed in 'stlport-target-class.construct'
> and additional requirements are in
> 'stlport-target-class.compute-usage-requirements'.

I'll take a look at that.

> > 4. Qt-Toolset
> > I'm trying to add support for qt-uic "embedding" feature.
> > This is used by Qt-Designer to embed *.png files in a C++ source
> > code. The files are compiled with the command line
> > uic -embed <unique id> <list-of .png files> - o embedded.cpp
> >
> > Thomas Witt and I have hacked some code for V1.
> > Can someone drop me a hint how I can start to implement this on V2.
> > And I thought I could add some more user friendliness on Win32
> > (library name, defines etc.)
>
> What interface do you plan for the "embedding" feature. I never used
> it (did not even know about it), so can't even imagine...

Mmh. Let me see.
When hacking V1, we simply added a list of .png Files to the target list
of the executable. This "png-Files list" is then "embedded" as
described above and the resulting .cpp is compiled into the
application.
Well, I think we could try:

embed-images unique-id : image1.png image2.png : embedded.cpp ;

exe app : main.cpp unique-id ;

and then call

uic -embed unique-id image1.png image2.png -o embedded.cpp

in order to created embedded.cpp.
I'd like to have "embedded.cpp" optional and defaulting to
"unique-id.cpp".

I hope this is a reasonably syntax.

Could you drop me some links to get more information about "hacking"
bjam ?

Yours,

Jürgen

- --
* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau
* voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover
* fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover
* hunold_at_[hidden] ! www.ive.uni-hannover.de

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/CRn0ljbJ/LLrxrYRAvFxAKDTof2zAx3OwPFLINuFPkkAW1Nx9wCdEK5N
avECc18zJJkK0tkqzBhs9AE=
=49py
-----END PGP SIGNATURE-----