Closed PierreCAMILLI closed 7 months ago
Please try /print('hello') instead of double quotes for your print argument.
Also, no arguments options should work here is some code we have:
[CommandLine.Option("nounittest", @"Disables unit tests.")]
public static void CommandLineNoUnitTests()
{
UnitTest.Settings.Enabled = false;
}
We are calling sharpmake with /nounittest to activate this one.
I tried to reproduce your issue and it looks like its related to the fact that MyArgument is in the global namespace. If you move MyArguments class into a namespace. It fix the issue. So I believe the issue here is that Sharpmake command line parsing code is broken for object in the global namespace.
@PierreCAMILLI Does the answer from Sylvain solves your problem?
Hi,
I'm sorry, the scope changed on our project, we no longer work on this subject and I can't access the work previously done about it.
You can close this issue.
Thank you for your answers
Hi,
I'm testing features offered by SharpMake but it seems custom arguments don't work as intended.
Executed with this command:
Sharpmake.Application.exe /sources('main.sharpmake.cs') /verbose /generateDebugSolution /hello
This gives me the following output which complains about compatibility issues between arguments despite the ones indicated are the same:
The same happens when I specify an argument:
There also seem to be an issue with how temporary C# files are generated in my Temp folder. An anonymous namespace is generated: