Nic,
Unfortunately I am not well versed in either ant or autoconf configury.
I personally build the different versions by changing the JAVA_HOME
environment variable to point to the jdk I wish to use for building.
Ant then picks it up and does the 'right' thing. I personally haven't
tried building with gcj yet and I don't know if ant has support for gcj.
In general I would say that the driver has moved away from autoconf/make
and towards ant as the build mechanism. The role make now plays is
essentially just the wrapper around ant that ties into the overall
postgres build mechanism.
thanks,
--Barry
Nic Ferrier wrote:
> Oh woe! the awful plight of the java build maker.
>
> The jdbc build works really well, for the majority of cases. But I'm
> just playing with building postgresql with GCJ (the GNU java
> compiler).
>
> The build is badly broken when it comes to dealing with GCJ:
>
> - the compiler is not passed through to the ANT build, it's not even
> autodetected.
> It's fairly easy to fix this problem though, but it would normally
> entail switching to the autoconf java macros for java compiler
> detection.
>
> - the version of the library to build is decided by testing the
> version of java that is running ant, not the version of java that
> is being used as the compiler.
>
> - the version of java is used to decide which version of the drivers
> get built. This prevents cross compiling.
>
>
> If this was an autoconf/automake build we'd use some macros to decide
> which version to build by running a small compile to check what
> classes were available.
>
> I could write an autconf/automake build... but it's never going to
> make ant redundant because windows people use ant (I'm guessing).
>
>
> Does anyone have any ideas how I might make the build process more
> generic whilst not breaking ant compatibility?
>
>
>
> Nic
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
