Date: Mon, 29 Mar 2004 01:12:23 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 329 ************************************************** Sunday 28 March 2004 Number 329 ************************************************** Subjects for today 1 Re: Building Make v3.79.1 : John Poltorak 2 Building DLLs : Stefan Neis **= Email 1 ==========================** Date: Sun, 28 Mar 2004 15:14:18 +0000 From: John Poltorak Subject: Re: Building Make v3.79.1 On Sun, Mar 28, 2004 at 03:43:48PM +0200, Stefan Neis wrote: > On Sun, 28 Mar 2004, John Poltorak wrote: > > > Anyone know anything about a .deps directory or what creates it? > > Normally, you manually specify, which files a particular target depends > on, however for large projects it's tiresome to manually add dependencies > of C(++) files on header files that are included, so gcc has a special > switch which makes it generate those dependencies (based on include > directives) in a format suitable for inclusion by make. Those files are > often put into a .deps subdirectory. Any idea about what triggers this switch? It looks like it gets triggered on one system, but not on another. > > HTH, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 2 ==========================** Date: Sun, 28 Mar 2004 16:11:07 +0200 (CEST) From: Stefan Neis Subject: Building DLLs Hi, I'm currently fiddling with building DLLs for wxWindows and have been adding support for building libraries in both a.out and OMF format, both static libs and DLLs. However, when trying to build a.out DLLs I'm having problems with long symbols for different functions which share a "long" common prefix: gcc -Zdll ... complains about the symbols being identical, although they are not. Is that a limitation of a.out build (i.e. you just have to use -Zomf for such DLLs) or is there some special linker flag which would enable building a.out versions as well? Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'.