multiple openspades releases build allowed

[ghost]

this is not specificly an issue but when you only run make you get the executable binary and you coud basicly run it without any errors. and the command openspades in the terminal only executes the executable you compiled first. i could compile all releases. i first compiled 0.1.0 then i compiled 0.0.4 last. the command openspades only executed 0.1.0. significantly you dont need to use sudo make install. if you have path errors because it cant find stuff just log into the sudo account and run the command and it will find it automaticly.

[noway]

I suppose that would work if you had installed openspades before, yes, resource files from previous version would be used by the new version.

[feikname]

There is a workaround.

You can set OPENSPADES_RESOURCES in Cmake to point to an absolute path for each binary, and leave the default resources path empty. This way, there are no conflicts between versions.

The downside is that you'd have to recompile to change one of the binaries User Resource Directory or symlink it to a new location. Perhaps a relative path may also work, who knows.

This is what I am going to do from now on to keep 0.1.0 and the development version together