Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.4.0, 1.5 Pre-Release
-
None
Description
<p>In general it should be possible to compile a single *.vcxproj via command line and MSBuild without a solution file.</p><p>There are several issues in the current repository</p><ul><li>For reference to the baseclasses there is a mixed usage of relative paths ..\baseclasses and $(SolutionDir)</li><li>Using $(SolutionDir) is the blocking reason why *.vcxproj files can not be compiled, because there is not SolutionDir variable defined when compiling a project.</li><li>The folder ..\shared is always referred relative, so it's totally inconsistent to use the variable in the other cases.</li><li>For Debug and Release configurations two different paths are defined for linking to the baseclasses library (strmbase.lib & strmbasd.lib), while LiveMedia555<span style="color:#ff0000;">D</span>.lib and DvbCoreUtils<span style="color:#ff0000;">D</span>.lib are generated at ..\shared, strmbase.lib is generated within a baseclass subfolder. --> genarating this lib in ..\shared as well makes the additional path definition to the baseclasses subpaths obsolete</li><li>There are also various inconsistent usages of slash / and backslash \ , sometimes there are redundant spaces or a redundant definition of targetname, targetext and outdir as well as intdir, but all these cases should be fixed only if really required to minimize the merge conflicts.</li></ul>