fpcmkcfg tool kills fpc.cfg if commandline parameter equals -o fpc.cfg
Original Reporter info from Mantis: Bart @flyingsheep
-
Reporter name: Bart Broersma
Original Reporter info from Mantis: Bart @flyingsheep
- Reporter name: Bart Broersma
Description:
If you already have an fpc.cfg file and you run
fpcmkcfg.exe -o fpc.cfg
(in the folder where your fpc.cfg resides) your fpc.cfg is removed (actually a backup is created) and no new fpc.cfg is created (fpcmkcfg errors out).
Steps to reproduce:
C:\pp\bin\i386-win32>dir fpc.cfg
...
24-03-2019 00:31 7.572 fpc.cfg
C:\pp\bin\i386-win32>fpcmkcfg -o fpc.cfg
Saved old "fpc.cfg" to "fpc.bak"
Error: Directory of file "fpc.cfg" does not exists. User -p to force creation.
C:\pp\bin\i386-win32>dir fpc.cfg
...
Directory of C:\pp\bin\i386-win32
File Not Found
It just killed my fpc.cfg!
(Yes there is a backup)
This works however:
fpcmkcfg -o .\fpc.cfg
Additional information:
This works however:
fpcmkcfg -o .\fpc.cfg
I would say that fpc.cfg as commandline parameter should point to the
same file as .\fpc.cfg (as it would do in almost any other program).
I tried to add -v (verbose) to the parameterlist, but unfortunately fpcmkcfg does not tell me which directory does not exist.
Mantis conversion info:
- Mantis ID: 35271
- OS: Windows
- OS Build: 10
- Build: r41788
- Platform: i386
- Version: 3.3.1
- Fixed in version: 3.3.1
- Fixed in revision: 41860 (#93a3764c)