|
|
Post by oss003 on Jan 14, 2020 19:03:51 GMT
It is possible to fix using directories with spaces but using names with spaces can't be done.
I'll send Jonathan the updated batchfiles to work with directory names with spaces for the next release.
|
|
|
|
Post by lamptonworm on Jan 18, 2020 17:09:26 GMT
Hi, just curious - what is the issue with spacey names? I believe the tools in the chain all support spacey names when they are quoted. Just a thought! Cheers, LW.
|
|
|
|
Post by oss003 on Jan 20, 2020 9:43:43 GMT
Hi, just curious - what is the issue with spacey names? I believe the tools in the chain all support spacey names when they are quoted. Just a thought! Cheers, LW. This isn't working for filenames because the batch files are working with commandline parameters and a character after a space in the filename will be handled as parameter. Greetings Kees |
|
|
|
Post by lamptonworm on Jan 22, 2020 12:56:10 GMT
When the project name is passed into the batch file, is %* any use? If the only param is the filename, it will concatenate all 'parameters' (in our case the parts of spacey filename) into one value. e.g.
build.bat:
echo filename="%*"
c:\build.bat my spacey name
filename="my spacey name"
|
|
|
|
Post by oss003 on Jan 23, 2020 11:00:47 GMT
When the project name is passed into the batch file, is %* any use? If the only param is the filename, it will concatenate all 'parameters' (in our case the parts of spacey filename) into one value. e.g. build.bat: echo filename="%*" c:\build.bat my spacey name filename="my spacey name" This is handled as %1="my", %2="spacey" and %3="name". Sometimes in build.bat, another batchfile is called eg. MAKE %1 %2 %3 and then %2 and %3 are handled as parameters So please don't use spaces in the filenames ..... Greetings Kees |
|
|
|
Post by lamptonworm on Jan 23, 2020 19:53:28 GMT
Ah ok, thanks. I was only looking at the spectrum batch files. Cheers, LW.
|
|
