![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am building a project using MS VC++ 2005 (beta). |
|
Is there a way to build the project so that it contains all of the necessary libraries internally? |
|
how can I identify all of the libraries necessary for a dll to be used properly? |
#3
| |||
| |||
|
|
Troy Jennings wrote: I am building a project using MS VC++ 2005 (beta). Visual Studio Express 2005 was released a month and a half ago... Is there a way to build the project so that it contains all of the necessary libraries internally? Yes, but unless you're building GPL programs, you can't legally do it, for licensing reasons. Search the mailing list if you're tempted to argue about this. It's been discussed before. how can I identify all of the libraries necessary for a dll to be used properly? There are many freebie programs out there to do this. You might even have received one with VS Express, or the Platform SDK. They most commonly go by names like 'depends' and 'requires'. They are often command-line tools, but not always. Another one I know about is an Explorer shell extension called Inspect Exe, from Silurian Software. They want money for it, though. |
#4
| |||
| |||
|
|
is it even possible to make the .dll if you only have Microsoft SDK, .NET SDK 1.1 and VC++ Toolkit 2003 ? |
#5
| |||
| |||
|
|
I see no reason why not. You may have noticed that I dropped mention of the command-line only compilers from the web page. That's only because the VS Express 2005 is now out of beta, so I assume it will be vastly more popular. I've tried but there is alot of MSVC*.lib files missing, I'm not really a huge |
![]() |
| Thread Tools | |
| Display Modes | |
| |