Albert Chin <[EMAIL PROTECTED]> writes:
> So, in both cases, libz is not on the command-line used to create the
> shared library.
Yes, what I meant was that I took the "cc" line libtool expand to,
inserted "-lmysqlclient" and tried link it manually. and it worked.
Making me beleive it is a l
Hi
again!
For all interested
in native Windows binaries built with Autotools and mnay other interesting
things:
wgcc is a cross-compiler tool primarily written for
Microsoft's Interix. Its primary purpose is to produce native Windows binaries
(internally using the Microsoft Tool chain),
When building with wgcc there are a few benefits:
Wgcc uses the native windows compiler to build (so the code may or may not be
faster ;o)) and whats a lot more important: the debug information produced is
readable by visual studio, so you can debug the output. Gdb on windows (at
least on inter
j«ÌFlÌ×ÉAtêåTCgÅ·I
®S³¿o^§ÅïõÍÆEgbvNXI
K¸o èÜ·B
j«ÌFlÉͨàÌSͲ´¢Ü¹ñB
TCgÅÍAèØètðÛðó]·é«ÌÝðÐîµÄ¨èÜ·B
http://www.free-premium.com/sereb/Ps007/
j«ÌFlÍ«ÌFl©çT|[gª
On Tue, Sep 19, 2006 at 10:11:36AM +0200, Kent Boortz wrote:
>
> Albert Chin <[EMAIL PROTECTED]> writes:
>
> > So, in both cases, libz is not on the command-line used to create the
> > shared library.
>
> Yes, what I meant was that I took the "cc" line libtool expand to,
> inserted "-lmysqlc
On Tue, Sep 19, 2006 at 11:05:25AM +0200, Duft Markus wrote:
>
> For all interested in native Windows binaries built with Autotools
> and mnay other interesting things:
>
> wgcc is a cross-compiler tool primarily written for Microsoft's
> Interix. Its primary purpose is to produce native Window
Hm, really i started out porting from unix to windows using cccl, but it took
not too long to realize that cccl is far to less powerfull. Cccl is capable of
translating some command line options, not really much more. This doesn't mean
cccl is bad. If one doesn't need more than this, its perfect
"Duft Markus" <[EMAIL PROTECTED]> writes:
> Hi again!
>
> For all interested in native Windows binaries built with Autotools and
> mnay other interesting things:
I'm not sure whether this is on-topic for Boost; it seems of somewhat
borderline relevance. However, now that you've started the thr
"Duft Markus" <[EMAIL PROTECTED]> writes:
> When building with wgcc there are a few benefits:
>
> Wgcc uses the native windows compiler to build (so the code may or may
> not be faster ;o)) and whats a lot more important: the debug
> information produced is readable by visual studio, so you can de
What are the proper incantations to deploy libraries and executables
from a staging area (such that the rpath correctly points to the
deployment area)?
The following doesn't seem to work:
./libtool --mode=install install ${la} ${destination}/lib/${l}
./libtool --mode=finish
On Tue, Sep 19, 2006 at 03:32:58PM -0700, Noel Yap wrote:
> What are the proper incantations to deploy libraries and executables
> from a staging area (such that the rpath correctly points to the
> deployment area)?
>
> The following doesn't seem to work:
>
>./libtool --mode=install i
On 9/19/06, Albert Chin <[EMAIL PROTECTED]> wrote:
On Tue, Sep 19, 2006 at 03:32:58PM -0700, Noel Yap wrote:
> What are the proper incantations to deploy libraries and executables
> from a staging area (such that the rpath correctly points to the
> deployment area)?
>
> The following doesn't seem
On Tue, Sep 19, 2006 at 05:18:08PM -0700, Noel Yap wrote:
> On 9/19/06, Albert Chin <[EMAIL PROTECTED]> wrote:
> >On Tue, Sep 19, 2006 at 03:32:58PM -0700, Noel Yap wrote:
> >> What are the proper incantations to deploy libraries and executables
> >> from a staging area (such that the rpath correct
Hello Noel, Albert,
* Albert Chin wrote on Wed, Sep 20, 2006 at 05:36:45AM CEST:
> On Tue, Sep 19, 2006 at 05:18:08PM -0700, Noel Yap wrote:
> > On 9/19/06, Albert Chin <[EMAIL PROTECTED]> wrote:
> > >On Tue, Sep 19, 2006 at 03:32:58PM -0700, Noel Yap wrote:
> > >>
> > >>./libtool --mo
14 matches
Mail list logo
