Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29236 Discussions

Is there a limit to the number of projects in a solution?

OP1
New Contributor III
667 Views
I have about 13 projects in my solution (some are libraries, some are executables) and I am running into some bizarre LNK errors.
I am wondering if there is a limit to the number of projects you can have in one solution... If yes... what is it?

Thanks,

Olivier
0 Kudos
4 Replies
jimdempseyatthecove
Honored Contributor III
667 Views

Oliver,

I have a solution with 13 projects no problems.

You do have to get your dependencies correct and you have to be aware that modules produce a .mod file (similar to a precompiled header) and dependent on the contents of the module an .obj file containing the code and/or initialization data. The .mod file has to be in your include path and the .obj files have to be in a modules path. This was confusing to me at first.

The confusing thing is the _input_ path for modules is specified in the Fortran | Output Files property page under the assumption that theFortran compilation of your Main is the project producing the module .obj files. In my case and most likely yours the module .obj files (and .mod files)are created in a seperate project. The output path of the Main (or the librarian) has to include the output path of the project that was used to create the module .obj files.

Jim Dempsey
0 Kudos
MVP1
Beginner
667 Views
Quoting - opmkl
I have about 13 projects in my solution (some are libraries, some are executables) and I am running into some bizarre LNK errors.
I am wondering if there is a limit to the number of projects you can have in one solution... If yes... what is it?

Thanks,

Olivier
Oliver,

I have a solution with 44 projects. It's work fine.
0 Kudos
OP1
New Contributor III
667 Views
Jim,

Thanks for your answer - I was actually able to find the source of the error. As you pointed out, I didn't have my project dependencies updated (talk about a silly mistake...). So, all the input paths for my libraries and include files were correct, but I didn't check any of the boxes you get when you right click a project's icon then choose Project dependencies... I wasted an entire afternoon trying to understand why a seemingly innocent project was suddenly wreaking havoc in my solution.

Thanks again!

Olivier

0 Kudos
jimdempseyatthecove
Honored Contributor III
667 Views

Olivier,

Also note, when upgrading versions of software, occacionally the dependencies go away. Keep this in mind for problems after upgrade.

Jim
0 Kudos
Reply