[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dependencies not compiled in

From: Bastien ROUCARIES
Subject: Re: Dependencies not compiled in
Date: Sun, 28 Aug 2011 14:14:00 +0200

Do you know parity ? see http://sourceforge.net/projects/parity/ it is
exactly what you need and moreover is better from a loader point of
view. If we should support msvc I tyhink we must use this target.

Wine thinks to use it for wine under cygwin, and it regularly used at
my uni. LD_PRELOAD tricks is really nice. The only lack is the
#include_next pat but it could easilly added trhought a preprocessor.


On Sat, Aug 27, 2011 at 12:56 AM, Michael Goffioul
<address@hidden> wrote:
> On Fri, Aug 26, 2011 at 10:13 PM, Bruno Haible <address@hidden> wrote:
>> Michael Goffioul wrote:
>>> Windows+MSVC. I know this is not a gnulib target.
>> Yes. But it could become a gnulib target if the $CC wrapper script was agreed
>> upon in GNU. For example, if Automake would distribute it, like it 
>> distributes
>> a couple of other wrapper scripts.
>>> I'm using regular:
>>> ./autogen.sh
>>> ./configure
>>> make
>> Just curious: What values do you use for $CC, $CFLAGS, $CPPFLAGS,
>> $LDFLAGS in this setting?
> $CC = cc-msvc
> $CFLAGS = -MD -g -wd4244
> $LDFLAGS = -Wl,-debug
> "cc-msvc" is a MSVC compatibility wrapper[1] I developed over the past few 
> years
> in order to compile octave and all its deps using regular autotools
> (although I still
> need some post-processing of the libtool script, probably because of my lack 
> of
> knowledge of the internals of libtool). It's written in C++ and was
> initially largely
> inspired by cccl.
> Michael.
> [1] it provides MSVC with a GCC-like command-line interface.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]