CHANGE pdx name to use project name

[ninovanhooff]

This changes the pdx name from a hardcoded "playdate.pdx" to "wheelsprung.pdx" in my case.

For me, this fixes the simulate task. But perhaps that's because I changed the pdx name somewhere else, too?

Note that the example project also uses workspaceFolderBaseName in launch.json: playdate_example/.vscode/launch.json

[samdze]

Yeah the build config may need a few fixes.
For now the best choice is to name the build products the same as the project containing folder.

This is because it's the simplest way to make sure the VSCode launch config and the build process both align on the same (non static) pdx name.

[ninovanhooff]

Not sure I understand whether you agree with this change or that you want me to change something or abandon it.

This change will name the build product after the project folder, which is what you want, right?

[samdze]

Sorry! I agree with the idea, and most of the time your implementation would work, but there probably isn't a 100% guarantee the project name matches the project folder name.

It would be very uncommon to change folder name and lose sync, but I'd like to take this into consideration.
system/nimscript's thisDir() or projectDir() can be used to achieve full coverage.

[ninovanhooff]

Done, note that

• You might want to review all other usages of projectName() in the project and change where necessary
• I got two warnings for ambiguous calls in this file, for getEnv and fileExists. The match os and nimscript. Didn't touch them, clarify at your own discretion

[samdze]

This should be good to go for now, other uses of projectName() are related to Nim caches or cleaning stuff.
Thanks!