/generateDebugSolution does not work about sharpmake HOT 10 CLOSED

It looks like a problem with sharpmake source itself. I just tested adding /generateDebugSolution to both master and dev branche versions of UpdateSharpmakeProjects.bat after compiling locally, and with no local changes, and it works fine. What commit are you based off of and do you have any local changes to sharpmake itself?

from sharpmake.

Hullo Mr. Savoie - long time no see ;)

This is straight off master with zero changes

from sharpmake.

Hihi, been a while :D

How exactly are you building your binary? I tried again with a clean repo and built from Sharpmake.sln (using VS2017). If you do that and add /generateDebugSolution to UpdateSharpmakeProjects.bat(32) does that bat file run without error?

from sharpmake.

from sharpmake.

Hello @Nuclearfossil ,
I was having this same issue.
Once you compile the Sharpmake.Application from the solution, make sure that you copy the following files from the "Sharpmake.Application/bin/release" (or debug if you compiled debug) into the sharpmake.cs files of your build:

Then you can use a .bat file like this one to create the debug solution:

@echo off Sharpmake.Application.exe /sources(@"solution.sharpmake.cs") /verbose /generateDebugSolution pause

generatedebugsharpmakesolution.txt
(Change the .txt extension for .bat)

The reason why it was failing for me was because I did not copy the .pdb files, I guess to create a debug solution it needs them.
You can also do this from the .sln of the sharpmake source, but you would need to change some debug fields in the Sharpmake.Application properties (I do not know if this is actually what you want, let me know if it is)

Hope this helps,

Cheers.

from sharpmake.

I only just noticed this issue (also hi everyone! :) )
I had the same problem a few months back, and it turned out that the /generateDebugSolution commandline switch only worked for me if I compiled Sharpmake in Debug.

Not sure if that's still the case

from sharpmake.

There's definitely something odd going on, I have a setup closer to fpuma and it's been working flawlessly for the last year using the Release built binaries. My bat file just does the following:

call bin\Sharpmake.Application.exe "/sources(@"SharpMake\Main.cs") /verbose /generateDebugSolution"

And it's called from the root of my project. Not sure why I have the extra quotes in there, it seems to run fine if I remove them. I also have not problems running from the generated debug solution or running debug or release directly from the Sharpmake solutions either. In addition to the binaries that fpuma lists I'm also copying over Microsoft.Build.Utilities.v4.0.dll and Microsoft.VisualStudio.Setup.Configuration.Interop.dll.

(Hi Bryan!)

from sharpmake.

I got the same issue. Copying over all dlls and pdbs from my release build fixed it. Can somebody please update the documentation so that it is up to date?

from sharpmake.

It seems that even the release version needs Sharpmake.pdb. The reason is that Solution.cs file tries to get a source file for the DebugProject project used in Debug solution creation. It does so by utilizing StackTrace . The DebugProject however is located in DebugProjectGenerator.cs inside the Sharpmake source.
Without the pdb file, there is no source file info for that file, and the code throws an exception. Unfortunately using "Embedded" Debug symbols does not work, that was my first attempt at fixing it.
So the only solutions I can think of -apart from just shipping the .pdb file- would be either to externalize the parts of DebugProjectGenerator.cs which generate the Debug solution, or to rewrite the code in some way to work without the source file.

At the moment I don't have time to try either, so I just wanted to share my findings in case someone else wants to have a go at it.

from sharpmake.

Closing this, if you take the .zip files with the prebuilt sharpmake binaries it works :)

from sharpmake.