On Jan 23 10:18, jano trouba wrote:
> if I were to do the opposite :
>
> port entirley the project under cygwin using cygwin sockets and X and
> build the binaries with cygwin
>
> I would have to ship cygwin1.DLL (or is it cygwin2 ?) together with the
> binaries and pay a licence fee, wouldn'
OK... Finally I think everything is clear...
And just to be perfectly clear and on the safe side :
if I were to do the opposite :
port entirley the project under cygwin using cygwin sockets and X and
build the binaries with cygwin
I would have to ship cygwin1.DLL (or is it cygwin2 ?) toge
On Jan 23 00:28, jano trouba wrote:
> In the examples you gave me of different applications (Hello), they are
> both LINKED via cgwin.
Yes, but the results are different. When using the -mno-cygwin flag
your build native Windows applications, when not using that flag you
build Cygwin application
OK thanks a lot for your time and answer...
I read the User's Guide...
Almost everything is clear now...
I still have a last question :
In the examples you gave me of different applications (Hello), they are both
LINKED via cgwin.
Unfortunatley my project if a major GUI program (about 80 0
On Jan 22 17:25, jano trouba wrote:
> >If you create static libs which don't use Cygwin functions, then you're
> >build native Windows libs. That's no problem and has nothing to do with
> >Cygwin anymore. You're off the hook.
> >
> >If you build static libs which use Cygwin functions, your applic
Thanks Corinna for your answer.. It is not yet entirely clear for me...
.
This is a NO-NO on this list.
I apologize for that. As I said I discovered cygwin and your site this
weekend...
If you create static libs which don't use Cygwin functions, then you're
build native Windows libs. T
On Jan 22 16:21, jano trouba wrote:
> >From: Tim Prince
This is a NO-NO on this list.
http://cygwin.com/acronyms/#PCYMTNQREAIYR
> >You are going way beyond the scope of this list. A mingw .a library could
> >be linked into an MSVC build, since it tries to avoid conflicting run-time
> >l
From: Tim Prince <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: cygwin@cygwin.com
Subject: Re: Questions about porting from Linux to Windows...
Date: Mon, 22 Jan 2007 05:52:28 -0800
You are going way beyond the scope of this list. A mingw .a library could
be linked into an MSVC
[EMAIL PROTECTED] wrote:
Hello
I am in the process of porting a huge application (> 700 000 lines of
code ; C ; Unix/Linux) to Windows.
I will not be using cygwin to port the GUI, but the project is based on
lots of static libraries. Thus it prompted me with several questions,
both techni
Hello
I am in the process of porting a huge application (> 700 000 lines of code ;
C ; Unix/Linux) to Windows.
I will not be using cygwin to port the GUI, but the project is based on lots
of static libraries. Thus it prompted me with several questions, both
technical and commercial.
I wi
10 matches
Mail list logo