Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C3C2C12.7090102@syntrex.com> Date: Wed, 09 Jan 2002 12:40:02 +0100 From: Pavel Tsekov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Jean le Roux CC: egor duda Subject: Re: w32api header problems References: <20020109115348 DOT A14411 AT infosat DOT net> <67136319166 DOT 20020109130747 AT logos-m DOT ru> <20020109133833 DOT A20443 AT infosat DOT net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Jean le Roux wrote: > On Wed, Jan 09, 2002 at 01:07:47PM +0300, egor duda wrote: > >>Hi! >> >>Wednesday, 09 January, 2002 Jean le Roux jean AT infosat DOT net wrote: >> >>JlR> I need to include /usr/include/w32api/winbase.h in order to use the >>JlR> GetVolumeInformation(...) system call under windows. >> >>JlR> However, as i metioned in an earlier mail, DWORD seems to not be >>JlR> defined. I tracked DWORD's definition down to windef.h.. but it seems >>JlR> the whole include chain is a bit funny.. there are lots of >>JlR> inter-dependencies which are not satisfied. >> >>JlR> Does anyone have any words of wisdom to make life a little easier, or >>JlR> do I simply have to test for, and include, all the headers in w32api ? >> >>you ought to >> >>#include >> > > I've done this but seems to leave my code in a tangle :) > I suddenly have parse errors in my own header files, on normal > function declerations. I can only deduce that windows.h is leaving an > open ifdef or has unterminated strings or something silly. > > Anybody encounter this before? Any suggestions ? > I can put the compiler output online if someone wants to take a look, > and ofcourse some code snippets. It would be helpful :) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/