Re: the build

Nic,

I am not sure exactly what your design aims are - I personally tend to set
reasonable defaults if possible and let the individuals doing the compiling
override whatever they like.  If you can't set defaults then would it be
reasonable to build all configurations (at least those that are possible
with the available compiler)?

I noticed you haven't used the compiler attribute of the javac task.  Either
I have completely misunderstood what you are trying to do or you have a
specific reason for not doing this.

paul

----- Original Message -----
From: "Nic Ferrier" <nferrier@tapsellferrier.co.uk>
To: <pgsql-jdbc@postgresql.org>
Sent: Tuesday, April 15, 2003 8:19 PM
Subject: [JDBC] the build


> 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