[GEM-dev] more mingwoes32
Hans-Christoph Steiner
hans at at.or.at
Wed Aug 3 20:38:46 CEST 2011
On Aug 3, 2011, at 3:48 AM, IOhannes m zmoelnig wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2011-08-02 18:18, Hans-Christoph Steiner wrote:
>>
>> - the autobuild currently fails with "libtool: link: only absolute
>> run-paths are allowed"; according to a bit of googling, it seems like
>> this is indeed a problem with "prefix" not being an absolute path.
>> would
>> it do any harm, to set PREFIX to a(n absolute) value, rather than
>> set it
>> to ""?
>>
>>> Yes, it wouldn't put the files in the right place. These settings
>>> are
>>> used on Mac OS X and it works.
>
>
> well afaict, it doesn't work on w32 right now, and you are calling
> configure with special arguments for w32 anyhow, so i don't get the
> argument about OSX. linking works fundamentally different on OSX
> than on
> w32.
>
>> One thing that might make sense is to
>>> not set prefix in ./configure but only when running make.
>
> the problem is, that configure is doing fine, but make is failing :-(
>
> however, i still don't fully understand what you are trying to fix
> with
> an empty PREFIX.
> where is that empty PREFIX located? do you assume that it is in the
> current directory? is it meant to just be a void target, where files
> will vanish unnoticed? i'm just afraid that you are triggering
> undefined
> behaviour using an empty PREFIX.
>
> if the problem is install targets, you might want to set the
> - --includedir (despite common believe, this is not where configure
> will
> look for headers but where it will install headers to) and the --
> libdir
> flags in configure, in order to get the installation paths right.
>
> if this doesn't work (e.g.: the linker still fails), you could still
> override the installation paths during "make install" time (i don't
> see
> a necessity to do it during "make all" time), by setting "libdir",
> "pkglibdir" and/or "includedir".
>
> in any case i would either leave prefix alone, or set it to something
> meaningfull, e.g. "/".
I don't really care what combo of DESTDIR, prefix, libdir, pkglibdir,
etc. is used as long as things get installed correctly. The current
combo, with prefix=, has been working on Mac OS X for a while on other
build systems as well. Like for Pd itself, for example.
The files need to end up in /c/home/pd/auto-build/pd-extended/packages/
win32_inno/build/ . The installer will then take everything in that
directory and install it into %ProgramFiles%\pd. So DESTDIR is /c/
home/pd/auto-build/pd-extended/packages/win32_inno/build, then in
order to get everything in DESTDIR to end up installed in %ProgramFiles
%\pd, prefix has to be blank. Then
/c/home/pd/auto-build/pd-extended/packages/win32_inno/build/bin
will be installed as
%ProgramFiles%\pd\bin
.hc
----------------------------------------------------------------------------
Using ReBirth is like trying to play an 808 with a long stick. -
David Zicarelli
More information about the GEM-dev
mailing list