[CLOSED]The 'testall' program to see a menu of the available components together lazarus / 21-General ---------------------------------------------------------------------- Aruna · 2022-11-23 17:17 In the Lazarus Wiki I came across: https://wiki.freepascal.org/Component_Palette and if you scroll all the way to the very bottom of the page the last line says: Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i Try running the 'testall' program to see a menu of the available components together with small example test forms for most of them; then inspect the code to find out how they work! I tried to do that in the IDE by selecting Tools then Example Projects. Things work fine on Windows but on Linux I get this error:Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i Unable to write state file for project Project Error: Unable to create file "/usr/lib/lazarus/2.0.10/examples/lib\x86_64-linux/testall.compiled" After some investigation this is easy enough to resolve. I noticed the path after "/usr/lib/lazarus/2.0.10/examples/lib" has a backslash and for Linux we need a forward slash. Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i "/usr/lib/lazarus/2.0.10/examples/lib\x86_64-linux/testall.compiled" Now comes the interesting part. I wanted to make things work under Linux and thought let me clone the git repo and see what I may be able to do. I found one repository on Gitlab: https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/main/examples And another repository on Sourceforge: https://sourceforge.net/p/lazarus/laz.git/ci/main/tree/examples/ Neither repository has a file called "testall.lpi" which was very confusing to me. So I checked then double-checked under the examples folder in both repos and found nothing again. I would like to try and get things working under Linux but to do this I have to find the location of the "testall.lpi" file first. I also noticed the file is there in my Linux system at this location: Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i /usr/lib/lazarus/2.0.10/examples/testall.lpi My question is this, how does "testall.lpi' end up under my Linux filesystem where it does in the first place? And why is it not there in both Lazarus repositories? Voodoo magic again ? I have not yet fully searched through all the Make files and such so quite possible I may find how this is done but then again this is strange enough for me so I thought I will share what I found so far and ask for help here. ---------------------------------------------------------------------- KodeZwerg · 2022-11-23 20:05 By default, Lazarus create in your project folder, in that case "Examples", a folder called "lib" and in that another folder for the destination OS. Does that answer your text? ---------------------------------------------------------------------- Aruna · 2022-11-23 20:26 Quote from: KodeZwerg on November 23, 2022, 09:05:45 pmBy default, Lazarus create in your project folder, in that case "Examples", a folder called "lib" and in that another folder for the destination OS. Does that answer your text? Thank you KodeZwerg that answers a part of my question but my question is 'where' is this file 'testall.lpi' located in the Lazarus git repositories? I am unable to find it in the SourceForge repository or GitLab repository. So if it is not there in the repositories where is it being pulled in from? ---------------------------------------------------------------------- MarkMLl · 2022-11-23 20:39 Yes, I agree that's an interesting question. I've certainly got it on my own installation which was built from source, and that includes the lazarus-trunk version which was DLed via SVN before it was turned off. MarkMLl ---------------------------------------------------------------------- KodeZwerg · 2022-11-23 20:54 I just can guess that your current .lpi file will be generated by Lazarus itself for your platform during installation. All you need is a .lpr (project file) from that a .lpi (project information file) is spawned from. But as said, it is just a guess, maybe a lazarus guru can bring light in that mystery ---------------------------------------------------------------------- KodeZwerg · 2022-11-23 21:00 Quote from: MarkMLl on November 23, 2022, 09:39:32 pmYes, I agree that's an interesting question. I've certainly got it on my own installation which was built from source, and that includes the lazarus-trunk version which was DLed via SVN before it was turned off. MarkMLl A backup can be found here, dont use, just for educational purpose i share url. Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i https://github.com/svn2github/Lazarus/blob/master/examples/testall.lpi ---------------------------------------------------------------------- Aruna · 2022-11-24 10:23 Quote from: MarkMLl on November 23, 2022, 09:39:32 pmYes, I agree that's an interesting question. I've certainly got it on my own installation which was built from source, and that includes the lazarus-trunk version which was DLed via SVN before it was turned off. MarkMLl Hi Mark would you have a link to the source you used to build, please? ---------------------------------------------------------------------- Aruna · 2022-11-24 10:26 Quote from: KodeZwerg on November 23, 2022, 09:54:27 pmI just can guess that your current .lpi file will be generated by Lazarus itself for your platform during installation. All you need is a .lpr (project file) from that a .lpi (project information file) is spawned from. But as said, it is just a guess, maybe a lazarus guru can bring light in that mystery  Yes you could be right. It is quite possible Lazarus generates it at install time. I am going to send out a email on the Lazarus list and see if anyone out there has had this issue and found a resolution/fix. ---------------------------------------------------------------------- Aruna · 2022-11-24 10:29 Quote from: KodeZwerg on November 23, 2022, 10:00:50 pmQuote from: MarkMLl on November 23, 2022, 09:39:32 pmYes, I agree that's an interesting question. I've certainly got it on my own installation which was built from source, and that includes the lazarus-trunk version which was DLed via SVN before it was turned off. MarkMLl A backup can be found here, dont use, just for educational purpose i share url. Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i https://github.com/svn2github/Lazarus/blob/master/examples/testall.lpi Thank you for your help KodeZwerg. So it used to be in the repository but then something happened? I think I will just send a email out on the Lazarus list describing what I have found and hopefully someone will have a fix? ---------------------------------------------------------------------- Aruna · 2022-11-25 14:37 Hi I was informed on the Lazarus mailing list by Martin Frb that.. QuoteThe "testall" exists in the "fixes_2_2" branch. (Which is used for current releases). In the "main" branch the example folder was re-ordered. During this process the "testall" appears to have been removed. Not sure of the reasons... Maybe oversight, maybe because it did not work. If the latter, then likely a working version can be re-added. I did sent a query to the person behind the change, hopefully he can shine some light on this So I am closing this thread now. Thank you everyone for all your help.