Hi!
I'm currently working on porting my wgcc patches from 1.5.22 to HEAD
(*pfff*). Now recently i changed the default output of wgcc to a.exe, so
i have an extension for my exe's, since otherwise they don't really work
that good in some cases ;o)
However, no i realized, that the whole libtool tes
Hi,
How do I build a program before a library with automake and libtool?
By default, the library is being built first and that is not what I
want.
Thanks,
Bob Rossi
___
http://lists.gnu.org/mailman/listinfo/libtool
Hi again!
Sorry, i must correct myself. $EXEEXT *is* used *sometimes* and as far
as my situation is concerned, completely in the wrong places...
I made the func_exec type of functions intelligent enough to recognize
an exe with or without extension...
For example tagdemo does this:
func_require
Hi,
I'm writing a Makefile.am file for a library. When I do make, the
foo-config is in the build directory. However, when I do 'make install'
it doesn't go into the bin directory. Any idea how to force it to?
Reading the documentation for libtool and automake didn't seem to help.
Thanks,
Bob Ros
Hi,
I've got a quick question hopefully. I'm building pcre on windows. I've
been able to build it into a dll and link against it with a small
program. However, when I build a static library, and link it with a
small program, I get the missing symbols error.
I know the symbols are in the library
Bob Rossi wrote:
Hi,
I've got a quick question hopefully. I'm building pcre on windows. I've
been able to build it into a dll and link against it with a small
program. However, when I build a static library, and link it with a
small program, I get the missing symbols error.
I know the symbols
Bob Rossi wrote:
> I know the symbols are in the library because nm tells me so,
> $ nm -g /home/bobbybrasko/download/pcre/pcre/install/lib/libpcre.a|grep
> compile
> libpcre_la-pcre_compile.o:
> 5550 T _pcre_compile
Note here that this is just a regular symbol, as you would expect wit
On Fri, Jan 19, 2007 at 06:30:19PM -0800, Howard Chu wrote:
> The next question is, why is it looking for an import symbol instead of
> using the real symbol. The answer to that must lie in your header files;
> they probably declare the function to be a DLL export, which causes the
> compiler to
On Sat, Jan 20, 2007 at 12:42:36AM -0500, Bob Rossi wrote:
> On Fri, Jan 19, 2007 at 06:30:19PM -0800, Howard Chu wrote:
> > The next question is, why is it looking for an import symbol instead of
> > using the real symbol. The answer to that must lie in your header files;
> > they probably decla
Bob Rossi wrote:
On Fri, Jan 19, 2007 at 06:30:19PM -0800, Howard Chu wrote:
The next question is, why is it looking for an import symbol instead of
using the real symbol. The answer to that must lie in your header files;
they probably declare the function to be a DLL export, which causes th
Bob Rossi wrote:
> So, the correct way is to tell the author to remove the declspec's
> alltogether from the header file? That will work for both dynamic and
> static setup?
No, it's not the right way. The right way is to add -DPCRE_STATIC to
the CPPFLAGS. When linking against a DLL without __d
Brian Dessent wrote:
Bob Rossi wrote:
So, the correct way is to tell the author to remove the declspec's
alltogether from the header file? That will work for both dynamic and
static setup?
No, it's not the right way. The right way is to add -DPCRE_STATIC to
the CPPFLAGS. When linkin
12 matches
Mail list logo
