>> > As AGO pointed out, searching for libfreetype.dll is non-portable,
>> > dangerous, and silly.
>>
>> Not me, who is doing that, but one large SW open-source library.
>> Therefore it is clear, that it have to link with other libraries in the
>> system that it is using.
>
> Right, but that doesn'
On Thu, 16 Jun 2005, Peciva Jan wrote:
> > As AGO pointed out, searching for libfreetype.dll is non-portable,
> > dangerous, and silly.
>
> Not me, who is doing that, but one large SW open-source library.
> Therefore it is clear, that it have to link with other libraries in the
> system that it is
> As AGO pointed out, searching for libfreetype.dll is non-portable,
> dangerous, and silly.
Not me, who is doing that, but one large SW open-source library. Therefore it is
clear, that it have to link with other libraries in the system that it is using.
Things turned in to the OS ideas. And I am
On Mon, 13 Jun 2005, Peciva Jan wrote:
> [snip]
> (*) I am expecting that I have understood it well, that I can not link MSVC
> compiled applications and cygwin-gcc compiled DLLs.
And this is not completely true anymore either. There were some fixes in
the recent snapshots of Cygwin that allow c
On Wed, 15 Jun 2005, Peciva Jan wrote:
> >> >> our cross-platform application is working on Linux and Windows but
> >> >> not on Cygwin when X are installed. The problem has been tracked down
> >> >> and as a result: What is the reason for naming
> >> >> /usr/X11R6/bin/libfreetype.dll and not cygf
On Wed, 15 Jun 2005, [iso-8859-2] Pe?iva Jan wrote:
> I think, you are missing the point. This compatibility library breaks the
> compatibility with non-cygwin world (see the previous discussion). Therefore,
> I was asking, WHY is it prefixed lib* and not cyg* and WHEN will it be
> removed to get
On Tue, 14 Jun 2005, [iso-8859-2] Pe?iva Jan wrote:
> Thanks for the response. I am glad that cyg prefix is planned to be used
> everywhere. However, can you give me some hints when will be the package or
> the
> DLL probably removed?
When no other package has a dependency on XFree86-lib-compat.
>> >> our cross-platform application is working on Linux and Windows but
>> >> not on Cygwin when X are installed. The problem has been tracked down
>> >> and as a result: What is the reason for naming
>> >> /usr/X11R6/bin/libfreetype.dll and not cygfreetype.dll ?
>> >
>> > This is an old library f
On Tue, 14 Jun 2005, Peciva Jan wrote:
> >> our cross-platform application is working on Linux and Windows but
> >> not on Cygwin when X are installed. The problem has been tracked down
> >> and as a result: What is the reason for naming
> >> /usr/X11R6/bin/libfreetype.dll and not cygfreetype.dll
>> Hi,
>>
>> our cross-platform application is working on Linux and Windows but not on
>> Cygwin when X are installed. The problem has been tracked down and as a
>> result: What is the reason for naming /usr/X11R6/bin/libfreetype.dll and
>> not cygfreetype.dll ?
>
> This is an old library from the
On Mon, 13 Jun 2005, [iso-8859-2] Pe?iva Jan wrote:
> Hi,
>
> our cross-platform application is working on Linux and Windows but not on
> Cygwin
> when X are installed. The problem has been tracked down and as a result:
> What is the reason for naming /usr/X11R6/bin/libfreetype.dll and not
> cyg
Hi,
our cross-platform application is working on Linux and Windows but not on Cygwin
when X are installed. The problem has been tracked down and as a result:
What is the reason for naming /usr/X11R6/bin/libfreetype.dll and not
cygfreetype.dll ?
We are using Coin for 3D rendering and it automatica
12 matches
Mail list logo
