I see, and gcc does that extra bit of linking itself, does it?

Victor
----- Original Message ----- 
From: "Michael Gogins" 
To: "Developer discussions" 
Sent: Saturday, February 16, 2008 12:59 PM
Subject: Re: [Cs-dev] MSVC build for 5.08 installer progress report


> The problem with Python modules failing to import was that the older
> SConstruct did not embed the manifest into the binaries. For that you need
> run mt, the manifest tool.
>
> The updated SConstruct does embed the manifests, and csnd and CsoundAC do
> now import. The following lines do the trick (all build environments 
> inherit
> from commonEnvironment):
>
> commonEnvironment['LINKCOM'] = [commonEnvironment['LINKCOM'],
> 'mt.exe -nologo -manifest ${TARGET}.manifest -outputresource:$TARGET;1']
> commonEnvironment['SHLINKCOM'] = [commonEnvironment['SHLINKCOM'],
> 'mt.exe -nologo -manifest ${TARGET}.manifest -outputresource:$TARGET;2']
>
> Regards,
> Mike
>
>
> ----- Original Message ----- 
> From: "victor" 
> To: "Developer discussions" 
> Sent: Saturday, February 16, 2008 5:23 AM
> Subject: Re: [Cs-dev] MSVC build for 5.08 installer progress report
>
>
>> What are/were the problems with the Python module (cnsd and/or CsoundAC)?
>> ----- Original Message ----- 
>> From: "Michael Gogins" 
>> To: "Developer discussions" 
>> Sent: Saturday, February 16, 2008 4:03 AM
>> Subject: [Cs-dev] MSVC build for 5.08 installer progress report
>>
>>
>>> Basically, everything is going fairly fast now.
>>>
>>> Everything builds except the OSC opcodes and the Pure Data external. I 
>>> am
>>> confident that I will also be able to build both of these.
>>>
>>> Csound runs, makes sound, and is debuggable -- it is true it is much 
>>> more
>>> easily debuggable than the MinGW build. csound5gui runs and makes sound.
>>> winsound runs.
>>>
>>> The Python interface runs.
>>>
>>> I now need to test the other stuff to see if it still works, and try
>>> debugging a Python module, and fix up the installer Python issue.
>>>
>>> There also will be a manifest/runtime library DLL issue, but I think I
>>> can
>>> fix it this time by including the runtime DLLs in properly named
>>> directories
>>> in the installation tree.
>>>
>>> Regards,
>>> Mike
>>>
>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net