Forum > General
Changes in fppkg. What's next?
(1/1)
zoltanleo:
I use:
* trunk Lazarus r60063 located here <my_dir>\lazarus_21_r60063\ (primary-config-path=<my_dir>\lazarus_21_r60063\_config)
* trunk fpc r40849 located here <my_dir>\fpc_r40849
* Win7 x64 Ultim
My fppkg.cfg is here <my_dir>\fpc_r40849\utils\fpcmkcfg and has such content
--- Code: Pascal [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---[Defaults]ConfigVersion=5LocalRepository=%LocalRepository%BuildDir={LocalRepository}build/ArchivesDir={LocalRepository}archives/CompilerConfigDir=%CompilerConfigDir%RemoteMirrors=https://www.freepascal.org/repository/mirrors.xmlRemoteRepository=autoCompilerConfig=defaultFPMakeCompilerConfig=defaultDownloader=FPCInstallRepository=user [Repository]Name=fpcDescription=Packages which are installed along with the Free Pascal CompilerPath=%GlobalPath%/{CompilerVersion}/Prefix=%GlobalPrefix% [IncludeFiles]FileMask=%CompilerConfigDir%/conf.d/*.conf [Repository]Name=userDescription=User-installed packagesPath={LocalRepository}lib/fpc/{CompilerVersion}/Prefix={LocalRepository}
Obviously there have been some changes in the use of fppkg, because when I initialize Lazarus I get this warning:
--- Quote ---"An error occurred during the initialization of Fppkg: Could not find a fpc executable in the PATH. Check your Fppkg configuration and restart Lazarus to be able to use Fppkg's functionality."
--- End quote ---
What should I change to avoid such a warning? I will be very grateful for the detailed and patient explanations.
zoltanleo:
Up
Zoran:
I have the similar problem.
I updated fpc 3.2-fixes (rev. 4138) and lazarus trunk (rev. 60458) and now I get "Error: the Fppkg configuration is corrupt."
Please see the attached picture.
Even more strange is that:
Lazarus 2.0-fixes does not have this problem when compiled with this fpc 3.2-fixes.
Lazarus trunk does not have this problem with fpc 3.0.4
Only the combination of Lazarus trunk and fpc 3.2-fixes. :o
Might be important to say that I do not have .fpc.cfg in my user folder, but each fpc version has its own in <fpc_install_folder>/lib/fpc/etc/fpc.cfg.
My system - Linux Mint 19.1 xfce 64-bit.
Cyrax:
--- Quote from: Cyrax on February 14, 2019, 01:23:15 pm ---To solve the fppkg problem, find the hidden .fppkg directory under at the users directory and inside that directory delete default file under config directory. Then at the dialog screen, which pops up when starting the Lazarus IDE first time or there is problem with not founding the FPC source directory or other things etc, tell fppkg to create a new configuration file.
--- End quote ---
Zoran:
--- Quote from: Cyrax on February 19, 2019, 02:19:11 pm ---
--- Quote from: Cyrax on February 14, 2019, 01:23:15 pm ---To solve the fppkg problem, find the hidden .fppkg directory under at the users directory and inside that directory delete default file under config directory. Then at the dialog screen, which pops up when starting the Lazarus IDE first time or there is problem with not founding the FPC source directory or other things etc, tell fppkg to create a new configuration file.
--- End quote ---
--- End quote ---
Hello, Cyrax, thank you for answering, but...
Although' it seems to work for fpc trunk, it does not for fpc-3.2-fixes :(
But, much more important is that even this fpc-trunk "solution" actually write fppkg.cfg directly under my user folder, outside its fpc installation folder. I cannot accept this as a solution, as I would not want fpc instances to interact with each other. They must not have common cfg files. As I said in my previous post:
--- Quote from: Zoran on February 19, 2019, 01:25:42 pm ---Might be important to say that I do not have .fpc.cfg in my user folder, but each fpc version has its own in <fpc_install_folder>/lib/fpc/etc/fpc.cfg.
--- End quote ---
I guess the same must be with fppkg.cfg.
Thank you again for trying to help.
Navigation
[0] Message Index