On 31/05/15 19:28, patspiper wrote: > On 31/05/15 19:01, Jonas Maebe wrote: >> You should do it the other way around: include the default fpc.cfg file >> (which is in a known location, since it's where FPC is installed) in >> your custom configuration file. That way you don't have to modify >> fpc.cfg every time a new fpc release (with a new fpc.cfg file) comes out. > I'll have to specify the location of fpc.cfg everytime I launch fpc. I > am not sure this solves my issue.
You can put this file in one of the default search directories for overrides. See http://www.freepascal.org/docs-html/user/usersu10.html for the list. Additionally, on Windows we now also look in the USERPROFILE and ALLUSERSPROFILE directories (the directories specified by those environment variables). >> You can modify the directories where the compiler looks for included >> configuration files using the "#CFGDIR xxx" directive inside >> configuration files. > This can be a good solution. I have just tested it and it worked. > > Is it documented anywhere? The online user manual doesn't mention it. > Google didn't catch it as well. It may be an omission in the manual. If so, please file a bug report about that. >> There is no way to specify "the directory where the >> current configuration file is located" though. > Is it possible to have such a feature although it is not crucial anymore? Adding non-crucial features is very low on the list, as they still need testing and maintenance. Jonas _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
