Re: [wxCode-users] wxCode bakefiles for unix (was Re: ANN: wxPdfDocument 0.5 released)

[Ulrich T. <Ulr...@gm...>]

Hi Francesco,

> > configure did not work since it believed that the makefiles were
> > created by bakefile 0.1.9 although I definitely created them with
> > 0.1.9.1. I changed the version number in autoconf_inc.m4 from 0.1.9
> > to 0.1.9.1. 
> yes; this is a bug in the latest version of bakefile which has already
> been solved in the CVS. I forgot to mention it, sorry. 

If it's not already there I would suggest to add this information to 
the wxCode maintainer guide.

> > 1) What changes are needed in my component's bakefile or elsewhere so 
> > that the BUILDDIR directory is created if it does not exist?
> that's not an easy thing like it could seem.

What a pity.

> In short, you should not use BUILDDIR != "." with autoconf since the
> author of Bakefile decided not to support automatic BUILDDIR creation
> with autoconf and it's not easy to add this manually. 

Ok, good to know.

> Thus I suggest you to use:
> <if cond="FORMAT!='autoconf'">
> <set var="BUILDDIR">$(FORMAT)$(WXLIBPOSTFIX)$(POSTFIX)</set>
> </if>

I'll adjust my component's bakefile. I'll experiment until I get 
something which works on Linux without too much difficulties.

The good news is, that wxPdfDocument compiles and runs on Linux without 
further problems (if the makefile is ok, that is).

> > 2) What changes are needed that the component's library name reflects 
> > for which wxWidgets build it was created?
> the libname should get the [u][d] postfix like it does on windows... but it won't use 
> exactly the same naming convention used by wx under unix... (i.e. 
> libwx_[gtk2,x11][u][d]_sublib-MAJOR.MINOR.so.0.RELEASE.0)

I'll check whether this works for my component tomorrow. Where can I 
set MAJOR, MINOR and RELEASE for my own component?

> the Makefile created by configure can be used only for the
> configuration you told to "./configure"... if you need to use another
> wx build, you should do a "make install" for that wx build and then
> relaunch your component's "configure" script.

Ah, ok, I understand. (I'm very new to Linux, you know.)

> The Makefile will be adapted to the currently installed build of wx
> (and here comes in the bug I told you in some previous mail: wx build
> flags detection is buggy in wxcode bakefiles since prior 2.6.2 it was
> not possible to detect them easily). 

Absolutely true. I built 4 different versions of wxWidgets (ANSI, ANSI 
DEBUG, UNICODE, UNICODE DEBUG). wxCode configure  said in the message 
UNICODE DEBUG but created a makefile for ANSI without DEBUG.

This will be corrected in 2.6.2?

I guess not every wxWidgets user will switch to 2.6.2 immediately. Is 
there a way to support pre 2.6.2 users?

> PS: I'm moving the thread from wxusers to wxcode since I think it's
> more relevant there. 

Right.

Thank you for your helpful responses!

Regards,

Ulrich
-- 
E-Mail privat:  Ulr...@gm...
E-Mail Studium: Ulr...@Fe...
World Wide Web: http://www.stud.fernuni-hagen.de/q1471341