X-Spam-Check-By: sourceware.org Message-ID: X-Sender: trouba_1 AT hotmail DOT fr In-Reply-To: <20070122175919.GA27843@calimero.vinschen.de> From: "jano trouba" To: cygwin AT cygwin DOT com Subject: Re: Questions about porting from Linux to Windows... Date: Tue, 23 Jan 2007 00:28:25 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 000 of the 700 000 total lines of code are X11/Motif code) which needs to run very fast (at times more than 40 000 graphical objects should change colors within a second) , and so having 2 depths of sending graphics events to the screen might be too much. That is why I was thinking about using a native GUI builder in order to port the GUI part, thus making the executable linked WITHIN the GUI builder using static ".a" libraries compiled with the cygwin environment, with the -mwindow flag... Thus my first questions about licensing policies and use of the cygwin DLL.... So if I understood correctly what you told me in your last message, if I follow the above-mentioned procedure I should be in the clear both in the licensing side (not needing any licence fee) and in the runtime side (not needing cygwin DLL) (the libraries should contain WIN32 code). Is this correct ?? _________________________________________________________________ Ten : Messenger en illimité sur votre mobile ! http://mobile.live.fr/messenger/ten/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/