Could you please update "6.3.1 Native Windows compilation" (http://ffmpeg.sourceforge.net/ffmpeg-doc.html#SEC25) in the ffmpeg documentation to point out that the following files have to be copied to "c:\mingw\bin" in order to get the build-script for shared-libraries/DLLs to work correctly on windows: Copy "lib.exe" and "link.exe" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin" to "C:\mingw\bin" Copy "mspdb71.dll" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE" to "C:\mingw\bin" Other versions of visual-studio might require slightly modified paths, and possible program-database filename, but the essence is the same. regards, Fredrik Orderud Ph.D student in Computer Science, NTNU
Fredrik Orderud wrote:
Could you please update "6.3.1 Native Windows compilation" (http://ffmpeg.sourceforge.net/ffmpeg-doc.html#SEC25) in the ffmpeg documentation to point out that the following files have to be copied to "c:\mingw\bin" in order to get the build-script for shared-libraries/DLLs to work correctly on windows:
Copy "lib.exe" and "link.exe" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin" to "C:\mingw\bin" Copy "mspdb71.dll" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE" to "C:\mingw\bin"
Other versions of visual-studio might require slightly modified paths, and possible program-database filename, but the essence is the same.
The doc update mentioned in my previous post takes this problem into account (by instructing people to put those files on their PATH). Martin -- Martin B?hme Inst. f. Neuro- and Bioinformatics Ratzeburger Allee 160, D-23538 Luebeck Phone: +49 451 500 5514 Fax: +49 451 500 5502 boehme at inb.uni-luebeck.de
Martin Boehme wrote:
Fredrik Orderud wrote:
Could you please update "6.3.1 Native Windows compilation" (http://ffmpeg.sourceforge.net/ffmpeg-doc.html#SEC25) in the ffmpeg documentation to point out that the following files have to be copied to "c:\mingw\bin" in order to get the build-script for shared-libraries/DLLs to work correctly on windows:
Copy "lib.exe" and "link.exe" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin" to "C:\mingw\bin" Copy "mspdb71.dll" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE" to "C:\mingw\bin"
Other versions of visual-studio might require slightly modified paths, and possible program-database filename, but the essence is the same.
The doc update mentioned in my previous post takes this problem into account (by instructing people to put those files on their PATH).
Martin
I am not sure that is a good idea since it would put *many* MS DLLs and EXEs on the MingW path. OTOH polluting the mingw bin with non-mingw stuff also stinks. I suggest creating a special-purpose c:\ms-for-mingw-bin to hold this stuff and putting *that* on the path. -- Michel Bardiaux R&D Director T +32 [0] 2 790 29 41 F +32 [0] 2 790 29 02 E mailto:mbardiaux at mediaxim.be Mediaxim NV/SA Vorstlaan 191 Boulevard du Souverain Brussel 1160 Bruxelles http://www.mediaxim.com/
Michel Bardiaux wrote:
Martin Boehme wrote:
Fredrik Orderud wrote:
Could you please update "6.3.1 Native Windows compilation" (http://ffmpeg.sourceforge.net/ffmpeg-doc.html#SEC25) in the ffmpeg documentation to point out that the following files have to be copied to "c:\mingw\bin" in order to get the build-script for shared-libraries/DLLs to work correctly on windows:
Copy "lib.exe" and "link.exe" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin" to "C:\mingw\bin" Copy "mspdb71.dll" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE" to "C:\mingw\bin"
Other versions of visual-studio might require slightly modified paths, and possible program-database filename, but the essence is the same.
The doc update mentioned in my previous post takes this problem into account (by instructing people to put those files on their PATH).
Martin
I am not sure that is a good idea since it would put *many* MS DLLs and EXEs on the MingW path. OTOH polluting the mingw bin with non-mingw stuff also stinks. I suggest creating a special-purpose c:\ms-for-mingw-bin to hold this stuff and putting *that* on the path.
Well... I guess there's a kind of a tradeoff here. Asking people to create a special path to put those EXEs and DLLs into and then adjust their PATH accordingly is probably more error-prone than simply asking them to call vcvars32.bat... OTOH, Microsoft _might_ put some EXE / DLL in those places in the future whose name conflicts with something MinGW needs... Martin -- Martin B?hme Inst. f. Neuro- and Bioinformatics Ratzeburger Allee 160, D-23538 Luebeck Phone: +49 451 500 5514 Fax: +49 451 500 5502 boehme at inb.uni-luebeck.de
Martin Boehme wrote:
Michel Bardiaux wrote:
Martin Boehme wrote:
Fredrik Orderud wrote:
Could you please update "6.3.1 Native Windows compilation" (http://ffmpeg.sourceforge.net/ffmpeg-doc.html#SEC25) in the ffmpeg documentation to point out that the following files have to be copied to "c:\mingw\bin" in order to get the build-script for shared-libraries/DLLs to work correctly on windows:
Copy "lib.exe" and "link.exe" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin" to "C:\mingw\bin" Copy "mspdb71.dll" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE" to "C:\mingw\bin"
Other versions of visual-studio might require slightly modified paths, and possible program-database filename, but the essence is the same.
The doc update mentioned in my previous post takes this problem into account (by instructing people to put those files on their PATH).
Martin
I am not sure that is a good idea since it would put *many* MS DLLs and EXEs on the MingW path. OTOH polluting the mingw bin with non-mingw stuff also stinks. I suggest creating a special-purpose c:\ms-for-mingw-bin to hold this stuff and putting *that* on the path.
Well... I guess there's a kind of a tradeoff here. Asking people to create a special path to put those EXEs and DLLs into and then adjust their PATH accordingly is probably more error-prone than simply asking them to call vcvars32.bat... OTOH, Microsoft _might_ put some EXE / DLL in those places in the future whose name conflicts with something MinGW needs...
Martin
Exactly where the various dirs end up in the path will depend on exactly when vcvars32.bat is called. In what file do *you* put the call? And what is *your* path after that? If the MS dirs are at the end of the path, all will be well. -- Michel Bardiaux R&D Director T +32 [0] 2 790 29 41 F +32 [0] 2 790 29 02 E mailto:mbardiaux at mediaxim.be Mediaxim NV/SA Vorstlaan 191 Boulevard du Souverain Brussel 1160 Bruxelles http://www.mediaxim.com/
Michel Bardiaux wrote:
Martin Boehme wrote:
Michel Bardiaux wrote:
Martin Boehme wrote:
Fredrik Orderud wrote:
Could you please update "6.3.1 Native Windows compilation" (http://ffmpeg.sourceforge.net/ffmpeg-doc.html#SEC25) in the ffmpeg documentation to point out that the following files have to be copied to "c:\mingw\bin" in order to get the build-script for shared-libraries/DLLs to work correctly on windows:
Copy "lib.exe" and "link.exe" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin" to "C:\mingw\bin" Copy "mspdb71.dll" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE" to "C:\mingw\bin"
Other versions of visual-studio might require slightly modified paths, and possible program-database filename, but the essence is the same.
The doc update mentioned in my previous post takes this problem into account (by instructing people to put those files on their PATH).
Martin
I am not sure that is a good idea since it would put *many* MS DLLs and EXEs on the MingW path. OTOH polluting the mingw bin with non-mingw stuff also stinks. I suggest creating a special-purpose c:\ms-for-mingw-bin to hold this stuff and putting *that* on the path.
Well... I guess there's a kind of a tradeoff here. Asking people to create a special path to put those EXEs and DLLs into and then adjust their PATH accordingly is probably more error-prone than simply asking them to call vcvars32.bat... OTOH, Microsoft _might_ put some EXE / DLL in those places in the future whose name conflicts with something MinGW needs...
Martin
Exactly where the various dirs end up in the path will depend on exactly when vcvars32.bat is called. In what file do *you* put the call?
The doc I wrote says to put it in msys.bat.
And what is *your* path after that? If the MS dirs are at the end of the path, all will be well.
Unfortunately, vcvars32.bat _pre_pends its own directories to the PATH... Martin -- Martin B?hme Inst. f. Neuro- and Bioinformatics Ratzeburger Allee 160, D-23538 Luebeck Phone: +49 451 500 5514 Fax: +49 451 500 5502 boehme at inb.uni-luebeck.de
Martin Boehme wrote:
Michel Bardiaux wrote:
Martin Boehme wrote:
Michel Bardiaux wrote:
Martin Boehme wrote:
Fredrik Orderud wrote:
Could you please update "6.3.1 Native Windows compilation" (http://ffmpeg.sourceforge.net/ffmpeg-doc.html#SEC25) in the ffmpeg documentation to point out that the following files have to be copied to "c:\mingw\bin" in order to get the build-script for shared-libraries/DLLs to work correctly on windows:
Copy "lib.exe" and "link.exe" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin" to "C:\mingw\bin" Copy "mspdb71.dll" from "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE" to "C:\mingw\bin"
Other versions of visual-studio might require slightly modified paths, and possible program-database filename, but the essence is the same.
The doc update mentioned in my previous post takes this problem into account (by instructing people to put those files on their PATH).
Martin
I am not sure that is a good idea since it would put *many* MS DLLs and EXEs on the MingW path. OTOH polluting the mingw bin with non-mingw stuff also stinks. I suggest creating a special-purpose c:\ms-for-mingw-bin to hold this stuff and putting *that* on the path.
Well... I guess there's a kind of a tradeoff here. Asking people to create a special path to put those EXEs and DLLs into and then adjust their PATH accordingly is probably more error-prone than simply asking them to call vcvars32.bat... OTOH, Microsoft _might_ put some EXE / DLL in those places in the future whose name conflicts with something MinGW needs...
Martin
Exactly where the various dirs end up in the path will depend on exactly when vcvars32.bat is called. In what file do *you* put the call?
The doc I wrote says to put it in msys.bat.
And what is *your* path after that? If the MS dirs are at the end of the path, all will be well.
Unfortunately, vcvars32.bat _pre_pends its own directories to the PATH...
Martin
"Unfortunately" means you're quite aware of the danger. Is there a way around that? -- Michel Bardiaux R&D Director T +32 [0] 2 790 29 41 F +32 [0] 2 790 29 02 E mailto:mbardiaux at mediaxim.be Mediaxim NV/SA Vorstlaan 191 Boulevard du Souverain Brussel 1160 Bruxelles http://www.mediaxim.com/
Michel Bardiaux wrote:
Martin Boehme wrote:
Michel Bardiaux wrote:
Martin Boehme wrote:
Michel Bardiaux wrote:
Martin Boehme wrote:
Fredrik Orderud wrote:
> Could you please update "6.3.1 Native Windows compilation" > (http://ffmpeg.sourceforge.net/ffmpeg-doc.html#SEC25) in the > ffmpeg documentation to point out that the following files have > to be copied to "c:\mingw\bin" in order to get the build-script > for shared-libraries/DLLs to work correctly on windows: > > Copy "lib.exe" and "link.exe" from "C:\Program Files\Microsoft > Visual Studio .NET 2003\Vc7\bin" to "C:\mingw\bin" > Copy "mspdb71.dll" from "C:\Program Files\Microsoft Visual Studio > .NET 2003\Common7\IDE" to "C:\mingw\bin" > > Other versions of visual-studio might require slightly modified > paths, and possible program-database filename, but the essence is > the same.
The doc update mentioned in my previous post takes this problem into account (by instructing people to put those files on their PATH).
Martin
I am not sure that is a good idea since it would put *many* MS DLLs and EXEs on the MingW path. OTOH polluting the mingw bin with non-mingw stuff also stinks. I suggest creating a special-purpose c:\ms-for-mingw-bin to hold this stuff and putting *that* on the path.
Well... I guess there's a kind of a tradeoff here. Asking people to create a special path to put those EXEs and DLLs into and then adjust their PATH accordingly is probably more error-prone than simply asking them to call vcvars32.bat... OTOH, Microsoft _might_ put some EXE / DLL in those places in the future whose name conflicts with something MinGW needs...
Martin
Exactly where the various dirs end up in the path will depend on exactly when vcvars32.bat is called. In what file do *you* put the call?
The doc I wrote says to put it in msys.bat.
And what is *your* path after that? If the MS dirs are at the end of the path, all will be well.
Unfortunately, vcvars32.bat _pre_pends its own directories to the PATH...
Martin
"Unfortunately" means you're quite aware of the danger. Is there a way around that?
Well... either 1. Change vcvars32.bat or 2. Ask people to put the relevant directory in the PATH themselves. I think 2. would be preferable if we do decide to change the "recommended procedure". Martin -- Martin B?hme Inst. f. Neuro- and Bioinformatics Ratzeburger Allee 160, D-23538 Luebeck Phone: +49 451 500 5514 Fax: +49 451 500 5502 boehme at inb.uni-luebeck.de
participants (3)
-
boehme＠inb.uni-luebeck.de -
fredrik.orderud＠idi.ntnu.no -
mbardiaux＠mediaxim.be