-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20-Oct-2001 Peter Eisentraut wrote:
>> How do distributors that need to build all driver types proceed ?
>
> I haven't seen one yet, but theoretically they should configure several
> different build trees from one source tree. Of course, this do
On Sat, Oct 20, 2001 at 04:15:56AM +0200, Gunnar Rønning wrote:
> * Marko Kreen <[EMAIL PROTECTED]> wrote:
> |
> | * driver type is researched in configure, which is the
> | right place for it.
>
> How do distributors that need to build all driver types proceed ?
>
> Compile for each platform
Gunnar Rønning writes:
> How do distributors that need to build all driver types proceed ?
I haven't seen one yet, but theoretically they should configure several
different build trees from one source tree. Of course, this doesn't work
with Ant, but it's trivial with GNU make.
--
Peter Eisent
* Marko Kreen <[EMAIL PROTECTED]> wrote:
|
| * driver type is researched in configure, which is the
| right place for it.
How do distributors that need to build all driver types proceed ?
Compile for each platform in different environments ?
--
Gunnar Rønning - [EMAIL PROTECTED]
Senior Consu
I thought about the issue, then hacked a bit and
the result seems to be quite edible:
* spec.{jdbc1,jdbc2,jdbc2e} files which describe
contents of different driver editions. So main
Makefile is very straightforward.
* make builds all source in one go, thus:
. avoids hell when old .jar
