From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Adam H(dot) Pendleton" <fmonkey(at)fmonkey(dot)net> |
Cc: | <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Autoconf options |
Date: | 2003-06-20 21:04:17 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B0F5@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
-----Original Message-----
From: Adam H. Pendleton [mailto:fmonkey(at)fmonkey(dot)net]
Sent: 20 June 2003 17:34
To: Dave Page
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: [pgadmin-hackers] Autoconf options
This would require modification of the symlink to switch
between release
and debug versions of wxWindows which should certainly
have the same
headers. I agree having multiple versions of WX is bad
in general (and
if you're clever enough to do it, you should be able to
fix the
resulting mess), but debug & release versions should be
permitted imho.
Okay, I will add the --with-wx-config=FILE option so that a
wx-config file can be specified explicitly. This should allow
side-by-side linking against debug and release. Without that option
specified, release will be the default, and debug will be linked against
in --enable-debug is passed. One question, what if the symlink
wx-config points to a debug version of wxWindows, but they don't specify
--enable-debug or --with-wx-config. We would then link against a debug
version of the wx library, but release versions of stc and xrc. Do we
care?
No. I would say just use wx-config as we do now in all cases, unless
overridden by the user.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-06-20 21:06:41 | Re: I'm Back |
Previous Message | Andreas Pflug | 2003-06-20 20:51:20 | Re: CVS version does not compile |