How do I make one project in VS depend on another

[indigo0086]

I made two projects, one a onsole app, and on a C++ shared library project.

I set the project dependencies on the console app to the shared library, so when it builds the shared library is built. I added the name of the .dll binary to the "additional dependencies in the console app. But in the .cpp file containing main, I reference the .h file for the library but when I try to compile it can't locate the file. How do I get it to load the file.

[Salem]

Did you also specify the path to the library header file?

Three separate fields may need to be filled in
- path to header file
- path to library file
- name of library file

[indigo0086]

-in my dll project I set the output path to a distrib folder in the root, along with the obj. and other files.
-in my console project I set the additional folders to that distrib folder, and also to the dll project path to look up the header.
-In the console project I added to the aditional dependencies the name of the dll that the dll project outputs.

When I compile I get an "fatal error LNK1104: cannot open file 'Direct3DUtilities.dll'"

Even though the paths are set.

[Elysia]

Erm, does that mean the file is open / in use?
Because the linker will not attempt to open the .dll file when linking with it (in your console project). Only when it's built.
And for the record, you only need to set a dependency to the project in the settings (and possible an additional include path to the header). Nothing else should have to be set.

[indigo0086]

I set the path correctly it's just not finding the dll. I mean does the project only need the .dll file or some other ones? does the manifest/obj file and other stuff need to be put in that folder.

[Akkernight]

You need to have the .dll in the same folder as your application's .exe is/are ...
If you're using MS VS C++ then the only thing I had to do was, make the projects depend on each other correctly, set the linker to search for libraries at the folder where your libraries are ( The compiler reads the object libraries and export libraries ) then link the compiler to the folder(s) where your headers are stored...

[indigo0086]

I've done all that, it's just throwing this fatal error when I try to compile. I set the dependency to the project, so when I build the console app it builds the dependant project, I then set the dll in my linker additional dependencies, then set the folder for the header files. It's just always saying it can't open the dll file.

[Elysia]

When does the error occur? When you compile or when you try to run it?
And if it's a compile error, for which project? The dll or the other?

[indigo0086]

When I try to compile the Console project that depends on the dll project. I can compile the dll project fine, it dumps the files in the propper directory, I can see them. When I try to compile the console project it throws an error.

[indigo0086]

Here's a visual

[Akkernight]

as I said earlier, the compiler reads the .lib files, not the .dll, that's read at run time...

[indigo0086]

my project doesn't output the lib files

[indigo0086]

So I narrowed the issue down to me having to use this stupid DLL Export bulls*** to create a .lib file.

Is there an alternate way to create a .lib file so I can use standard C++ again?

Even though I do the exporting and including the .lib file that is generated it's still complaining about not being able to open it.

[abachler]

In VS Express 2008, have both projects in the same solution, then right click the dependant project and select Project Dependencies, then check the projects it is dependant on.

[indigo0086]

I've done that, my visual studio must be broken.