X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Cc: cygwin AT cygwin DOT com Message-Id: <4B9F5721-3E33-41EE-93C6-A3B6CEB5D485@cern.ch> From: Georg Troska To: worwor AT bellsouth DOT net, Andy Koppe , "Charles D. Russell" , Dave Korn In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Subject: Re: mingw headers and libraries missing Date: Wed, 29 Jul 2009 10:53:54 +0200 References: <5FE114CB-1BD5-450B-BE50-27D7D665CB7D AT uni-dortmund DOT de> <416096c60907271220x50eaca35nc454c41ad6a92d76 AT mail DOT gmail DOT com> <416096c60907271229n1f87acd0ha410da5dc8c51d54 AT mail DOT gmail DOT com> <4A6ECECC DOT 7030404 AT gmail DOT com> <5D074DD3-FF46-44EF-B015-59531A8D8DC3 AT uni-dortmund DOT de> <4A6EEA7B DOT 5060502 AT gmail DOT com> <4A6F15E8 DOT 80900 AT gmail DOT com> 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 Wow, sounds I have all the experts sitting together in this list. Maybe you can help me once more: First a brief plan: I'm working for the ATLAS-Collaborationand we need for detectordevelopment a programinterface. We have one really big and really old programm written in LabWindows C Code (of course in Windows) this is really a mess. And we have a big new program which is almost platform-independet (http://projects.hepforge.org/eudaq/ ). These programs shound communicate with each other. As the eudaq-code is running very well on cygwin I thought it would be easy to write a dll for accessing it from windows. The LabWindow-thing can handle this - I tried this out. So I changed the source-code a bit so that eudaq-software compiles with -mno-cygwin. In deed I get it compilable. But then the code is not running. For me two major problems have focussed out: I have a dependency on sys/selector.h and a dependency on pthread.h I think I can link against this external pthread-libraries (http://sourceware.org/pthreads-win32/ ). And I found a switch inside the code for linking against winsock(2).h This switch is for beeing compatible with Visual C++, which actually is not working. I'm not really sure if I can use the windows-like winsock environment in cygwin. Is it really compatible? What does this stuff with posix and so on mean in detail? What do you think? Is it easier to get this stuff running in cygwin or to make it possible in Visual C++? I would definetly prefer the first one. How far is the development of the windows cross-compiler really? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple