I just can't let some things go. I am such a bad boy.
See attachment. It has a great big TODO when working out BUILD_EXEEXT
that still needs implementing. Note that you need to change Makefile.in
as well to change "@TARGET_EXEEXT@" to "@EXEEXT@".
Tested as working on my system and configurati
Trying to get it to work correctly:
BUILD_CC is correctly determined, but BUILD_EXEEXT is not (unless you
have a Cygwin system). On closer examination, the system is in fact
natively building lemon and mksourceid but because the extension is
wrong, you get an error like:
make: *** No rule
Thanks for the reply.
To answer your question using autoconf/configure terminology, my build
system is Linux and my host system is MinGW32. That is I am building on
Linux to generate libraries/executables to run under MinGW (on Windows
essentially). I would however face exactly the same issue
On 12/6/17, Alastair Growcott wrote:
>
> To avoid confusion I recommend that you remove the option to
> cross-compile
I'm cool with that approach. Can you suggest a specific edit to the
configure.ac file that will accomplish what you describe?
>
> Also, I am not sure your suggestion of generati
Alastair Growcott wrote:
>
> Cross-compiling sqlite3 fails due to the use of binaries in the
> build process that are generated during the build process.
> Specifically:
>
You'll need to use the NMAKE macro XCOMPILE. Also, depending on
target platform you may need to use the other NMAKE macros l
On 12/4/17, Alastair Growcott wrote:
> Cross-compiling sqlite3 fails due to the use of binaries in the build
> process that are generated during the build process.
I recommend that you do
./configure; make sqlite3.c
or
nmake /f makefile.msc sqlite3.c
depending on whether your host sys
6 matches
Mail list logo
