I searched on Timo's 'xml option' for poide, but it just found his same post, so that didn't tell me anything.
What I'm doing is publishing some stable diffusion code on gethub and would like to present seperate project directories for Pelles C, gcc and VS.
I would like to, at least, have the executables all go into a 'release' directory that has the test harness already in-place for users to try out upon compilation.
Having the exe in it's default working directory with all it's files, for testing, isn't going to work.
I can control the exe directories in gcc and VS, but haven't found a way other than executing a batch file or hacking the project file (maybe) to control where Pelles drops the final exe.
It's not that big of a deal, but I'd like to give users a somewhat consistent set of directories in each project space to work with. I'll get it done, one way or another.
Along the same lines; Is there any 'gotchas' in distributing a Pelles project file?
Like previously embedded directory paths and such? Will they adapt to a new 'home' or do I have to do some manual cleanup?
Thanks again
