Pyd on Linux building woes

[Kirk McDonald]

Carlos Santander wrote:
> Kirk McDonald escribió:
> 
>>
>> Before I started mucking around with it, CeleriD simply took all of 
>> the code files needed, jammed them all on a command line with the 
>> appropriate options (-c, mostly), and compiled them. Then it linked 
>> them together. Fine.
>>
>> When adding gdc support, the first thing I realised was that gdc (and 
>> gcc) doesn't support DMD's -od option, and distutils requires that all 
>> of the object files be placed in a specific directory. My first stab 
>> at getting around this was to compile the sources one at a time, 
>> specifying the location of the object files one by one.
>>
>> When I tested this with DMD, it compiled but did not link. It 
>> complained of undefined symbols. The symbols given were the big long 
>> mangles of template instances. I am still not sure why this happened. 
>> I fixed it by putting it back the way it was, as a single call to the 
>> compiler.
>>
>> To get rid of the need for the -od option, I changed the current 
>> working directory to where the object files needed to go, and 
>> specified the full path to each of the source files. By not specifying 
>> a location, the object files just get dumped in the cwd. Problem solved.
>>
> 
> Not too helpful, but anyway: if you call gdc as "gdmd", it accepts dmd's 
> parameters (instead of gcc's). gdmd is just a wrapper script.
> 

I'm well aware of gdmd, but I have chosen to not use it. It is a perl 
script, and will not typically work on Windows. I eventually want to 
support using GDC on Windows.

-- 
Kirk McDonald
Pyd: Wrapping Python with D
http://dsource.org/projects/pyd/wiki