search

BlaatSchaapCode / visspel

MIT License
0 stars 0 forks source link

Sanitise output file paths #4

Closed a-v-s closed 2 years ago

a-v-s commented 2 years ago

For the time being, the GNU Makefile and MSbuild projects use a different output path / filename.

A consistent output file path would be desirable as for the binary to locate the data. As such, it may make sense to put the build configuration description in the filename,

eg.

out/visspel_linux_x86_64_gcc_debug
out/visspel_linux_x86_64_clang_debug
out/visspel_mingw64_x86_64_gcc_debug.exe
out/visspel_win32_x64_mscl_debug.exe

Note this example uses enviorement-specific architecture identifiers (eg. x86_64 vs x64) as this keeps the Makefile/MSbuild files the simplest.

In such way, the data directory, in the development environment, will be ../data/

a-v-s commented 2 years ago

Some implementation has been made, but they are not correct tuples.