X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=BAYES_00,SARE_RECV_SPAM_NAME2 X-Spam-Check-By: sourceware.org From: To: Subject: Using cygwin headers/libraries in MS compiled programs Date: Thu, 31 Dec 2009 18:25:20 +0800 Message-ID: <001b01ca8a03$90bfe2f0$b23fa8d0$@calgacus.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Folks, Apologies for the dumb question and please re-direct if there is a better forum. How do I use cygwin *.h and *.dll in MS console programs? If I include in a MS program I get many conflicts between the cygwin CRT and MS CRT stuff. Is my only options to "port" the headers to MS and dynamically load the cygwin functions with LoadLibrary()? What calling conventions do I need for cygwin functions in MS compiled code? All I really want is cygwin_conv_path() so that my MS programs can accept cygwin paths. Regards, Neil -- 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