Probably a stupid question, but what's the deal with this myproject.home and mps.macro.myproject.home-$myproject.home folder macro combination in build solutions. I am using it because I know you need...
This is an auto-generated question from the MPS Slack community: Probably a stupid question, but what's the deal with this myproject.home and mps.macro.myproject.home-$myproject.home folder macro combination in build solutions. I am using it because I know you need it (copying it from other build solutions), but I don't understand exactly what it does. If I search through the MPS source code, I find some tests that use the MPS_MACRO_PREFIX='mps.macro' string in test cases, so it must be a magical prefix, but I haven't found any explanatory text when googling for it.
6 comments
Sort by
Date
Votes
MPS JUnit integration will only pass along properties beginning with `mps.macro.` to the project.
Ah, so it's for testing, right? I've seen it used in the context of when people want to output generated code to a different location than the default build location
In my build solution I have:
'folder mps.macro.*my_project.home* = something'
And in my TestInfo file I have:
'ProjectPath: ${*my_project.home*}',
pointing in the settings to 'something'.
Do I understand it correctly that these are related? As in...
1. running tests from the commandline receives 'mps.macro.*my_project.home*'
2. MPS's junit integration passes this as 'my_project.home' to junit
3. And this is mapped on the ${my_project.home} in testinfo
4. and that is why testing works.
Or are these two completely unrelated?
yes, you got it right
That was quick :-) Thanks Slack user:U6K3FGW3U>
This is auto-generated question from the MPS Community Slack Workspace. If you want to comment on the question, do it from the Slack workspace
Post is closed for comments.