Lazarus
Programming => Packages and Libraries => Ported from Delphi/Kylix => Topic started by: taazz on March 08, 2013, 02:30:03 pm
-
I have ported this morning the gpStructureStorage components to lazarus/FreePascal. Running the tester application from Win32 it passes all the tests. I have removed all references to windows unit to make it cross platform and removed all windows requirements (I think I got them all).
I'm looking for testers on other operating systems. If interested go to https://sourceforge.net/projects/codelibrarian/ (https://sourceforge.net/projects/codelibrarian/) and download it either from the git repository or the Pre_Release folder in the files section.
The idea is to write the CodeLibrary Addin from GExperts as a standalone application for start and later to make it an addin for lazarus. You will find a pre-alpha version of the librarian in the repository as well.
Thank you.
-
Compile test on i386-linux passes, but I can't compile the tester since it uses 2 3rd party components that I don't have...
-
Ξ€ester only has buttons and check boxes no 3rd party controls at all.
Removed all false 3rd party dependencies from the tester application I uploaded the changes to git and the zip file.
Thank you for your input.
-
Ehm... see attached screenshot
-
Yeah sorry about that habits are difficult to break.
-
The first alpha version is up.
In this version the librarian executable is almost complete, the only thing left to do is the Import and merge of library files. everything should work opening existing libraries deleting folders and snippets creating new folders and snippets everything works so far.
Be careful with the deletion I haven't implement a confirmation dialog and if you select a folder it will delete everything in it regardless of the number of snippets or sub folders.
As always I have updated the repository and uploaded a zip file with the developing environment, this time I have uploaded and a win32 executable.
I'd appreciate if any one can build a linux or mac application and send it to me so I can upload it too.
Regards.
-
I cloned your git repo. It does not compile on Linux.
For example, there is UInt32, should be Cardinal.
If I make it compile, do you want a patch?
You could also install Linux easily on a virtual machine or using dual boot. If a code compiles on Linux then it has a high chance to compile on OS/X, too.
[Edit] I attached a patch. It compiles but does not work well. It crashes when trying to open or create something.
It may be caused by interfaces. What is the recommended compiler version.
Juha
-
Hi Juha,
I am using laz 1.0.6 fpc 2.6.2 , the components assume COM interfaces, so that has do be declared on all component units I think. Before compilling the librarian try executing the tester, if the tests are completed correctly then librarian should work.
I'll take a closer look on your patch and try it on my end.
-
Hmm trying to make heads or tails wit the patch your provided.
I'm new to git so this will take some time any hints on how to apply the patch other than manual?
-
I think I have applied all your code changes except the IFnDEF one which is just a cosmetic choice.
GIT repo has the latest code. Keep in mind that the above works on windows as you can see from the screen shot on the sf.net. The biggest change is that I removed the GpStuff unit completely now it as way to complicated to make it cross platform and on top of that I don't know assembly.
Try to see if the tester application reports problems before building the librarian. From the changes I see nothing that will change the current status.
I'm on a Intel Pentium M 1.6 GHZ with 1 GB of Ram that suffers from over heating any thoughts of VMs on this laptop brings in mind images of uncontrollable fire just below the key on the keyboard, close enough to burn your fingers but not close enough to see it in time. and disk space does not allow a second OS to be dual booted.
-
OK I have just downloaded a OpenSuse 11.3 vm and installed the vmware player on my laptop I'm overwhelmed by the things I have to adapt to for the time being in order to install lazarus and fpc 2.6.2 on that machine although yast seems easy enough to use (web reading for it not used it yet). for this project I think I'm going to install only fpc and its command line IDE and rewrite the tester as a console application and might extended to a unit testing application too if I manage. In any case the first for a linux debugging environment was made. I hope that I can find what is going on in there.
-
Hmm trying to make heads or tails wit the patch your provided.
I'm new to git so this will take some time any hints on how to apply the patch other than manual?
git apply 0001-Make-it-compile-on-Linux.patch
I will check your changes soon.
Juha
-
argh!!! Console mode linux managed to remember how to mount and external disk got lost on how to define that disk remembered the /dev folder got lost on all the contents in there found disk and finally managed to mount my external ntfs disk to linux. yeah!!! and that took me only 1 hour of searching
Now where is that linux pocket guide when I need it.......
in any case does the fpc install.sh needs to be started under a specific folder aka should I copy it in the users home directory for instance or it doesn't matter?
now what was the command to make a file executable on an ntfs drive?
off to find that pocket guide of mine.
EDIT:
I'm really impressed with suse 11 and I imagine 12 is even better, type a command and get a helpful push to the right direction eg that command exists in sbin your need root access or the command not found try cnf <command> etc it wend as far that the cnf proposed to me how to find and install the missing mc in a few minutes no need for my pocket guide now that I found it.
In other news I have fpc installed fp works and I have created my first (again) hello application. Now to copy the components over and start re writing the tester application.
gonna try that cnf on git :D, any idea why shutting down the system hangs the player? it seems that the vm is stuck on an infinite loop or something I have to kill the process. Oh Well that's a small price to pay I guess.
-
Well my test on OpenSuse 11.3 i386 indicate that everything works as expected. At least for the gpStructureStorage component. The only thing that comes to mind is you have a 64bit OS and you build a 64bit executable although I do not know why that would be a problem.
-
Uploaded a new version. This one has everything planned for the 1st release except the ability to move snippets and folders around to re arrange them in order you like. That will be the last ability before Version 1 so I'm calling this release a beta.
Now let me try to install lazarus on my linux and see if I can create a linux executable also.
BB.
-
I tried under FreeBSD 9.1 using FPC 2.7.1 - I must use 2.7.1 for FreeBSD, because there are lots of Threading and memory corruption issues in any released FPC version for FreeBSD.
Anyway, got your latest code and tried to compile the Tester project and got these errors.
/data/devel/tests/codelibrarian-code/Components/GpLists.pas(6423,22) Error: Incompatible types: got "TThreadID" expected "LongWord"
/data/devel/tests/codelibrarian-code/Components/GpLists.pas(6424,25) Error: Operator is not overloaded: "LongWord" = "TThreadID"
FLastThreadId is defined as a Cardinal, but GetCurrentThreadID under FreeBSD returns a TThreadID type which is a pointer to record structure. Slightly different to Linux or Windows.
Attached is a patch which will fix the compilation problem.
After this the Tester project compiled. When I ran "all tests", my system sat at 100% CPU load for a couple of minutes, then the application crashed out to the command prompt.
ps:
I would recommend you convert the Tester application to FPTest (Free Pascal Testing Framework). FPTest is a unit testing framework for exactly such needs. The Text Test Runner will give you progress output by default, and better results as to what worked, what doesn't and where it crashed. Test results can also be shown as XML or HTML output - see link below. FPTest also has a GUI Test Runner, but currently only for fpGUI. A LCL version is planned to.
FPTest code repository:
https://github.com/graemeg/fptest (https://github.com/graemeg/fptest)
Some FPTest information and usage examples:
http://wiki.freepascal.org/FPTest (http://wiki.freepascal.org/FPTest)
Sample HTML test result output (actual test output for tiOPF project):
http://opensoft.homeip.net/tiopf/unittests/freebsd64.html (http://opensoft.homeip.net/tiopf/unittests/freebsd64.html)
-
Thank you graeme for the patch.
I'll download 2.7.1 and run some tests and see what I'll come up with.
-
Some more info, I have installed fpc 2.7.1 on windows32 and compiled the tester application, Storage Truncation test fails with 2.7.1 with a message of access denied I'm guessing it has something to do with the way fpc frees non referenced interfaced objects. I do not if it is possible to work around that problem probably a local procedure might solve it. The problem seems Freebsd specific I'm searching for vm with freebsd preinstalled to see if I can reproduce it. I'll keep you posted.
-
I have run more test on linux and created two executables for i386 one with gtk and one with QT as far as I have tested it it seems to work as expected. I haven't been ample to install freebsd and fpc 2.7.1 to test it on that platform as well so for now the only official supported fpc version is 2.6.2. Next step is a freeBSD VM and a 2.7.1 fpc installation any hints for a quick installation? Bigchimp FPCUP works with freebsd?
-
Bigchimp FPCUP works with freebsd?
Haven't tried it yet, don't think so. Shouldn't be too hard to fix it though.
-
Modified fpcup for FreeBSD, NetBSD - no testing though. (posted to fpcup thread as well)
If you want to compile, run & report problems, I'd be very grateful. If you don't - no problem either ;) I'll get round to setting up a FreeBSD VM and doing it myself.
Things that may be wrong/tricky:
gnutar may not be available by default; the bunzip2 executable may have a different name and unzip may not be available by default either (so those should be installed in advance)
installercore.pas
@@ -180,6 +180,12 @@
+ {$IFDEF BSD} //Includes FreeBSD, NetBSD, OpenBSD
+ //todo: freebsd: check
+ FBunzip2 := 'bunzip2';
+ FTar := 'gnutar'; //check if available
+ FUnzip := 'unzip'; //unzip needed at least for FPC chm help
+ {$ENDIF BSD}
Check for valid bunzip2: hopefully bunzip2 --help works on FreeBSD and returns status code 0. If not, the code will need to be changed with an {$IFDEF BSD} or FREEBSD
@@ -296,6 +302,7 @@
OperationSucceeded := CheckExecutable(FBunzip2, '--help', '');
installerfpc.pas:
Extraction of a bootstrap compiler section. Basically copied from Linux section.
There's a chance the parameters for the exes are different in which case the code needs to be fixed.
@@ -478,6 +478,32 @@
+ {$IFDEF BSD} //Includes FreeBSD, OpenBSD, NetBSD
+ //todo: test parameters
+ //Extract bz2, overwriting without prompting
+ if ExecuteCommand(FBunzip2+' -d -f -q '+BootstrapArchive,FVerbose) <> 0 then
+ begin
+ infoln('Received non-zero exit code extracting bootstrap compiler. This will abort further processing.',eterror);
+ OperationSucceeded := False;
+ end
+ else
+ begin
+ ExtractedCompiler:=BootstrapArchive+'.out'; //default bzip2 output filename
+ OperationSucceeded := True; // Spelling it out can't hurt sometimes
+ end;
+ // Move compiler to proper directory; note bzip2 will append .out to file
+ if OperationSucceeded = True then
+ begin
+ infoln('Going to move ' + ExtractedCompiler + ' to ' + FBootstrapCompiler,etinfo);
+ OperationSucceeded:=MoveFile(ExtractedCompiler,FBootstrapCompiler);
+ end;
+ if OperationSucceeded then
+ begin
+ //Make executable
+ OperationSucceeded:=(fpChmod(FBootStrapCompiler, &700)=0); //rwx------
+ if OperationSucceeded=false then infoln('Bootstrap compiler: chmod failed for '+FBootstrapCompiler,etwarning);
+ end;
+ {$ENDIF BSD}
Thanks,
BigChimp
-
Modified fpcup for FreeBSD, NetBSD - no testing though. (posted to fpcup thread as well)
+ FTar := 'gnutar'; //check if available
The default tar is "tar". Since FreeBSD 8, it also supports some newer gnu commands like --strip FreeBSD7 is EOL since 2012-02-28 (but there is a 2.6.2 for it)
Try to use it as much as possible. GNU tar, if available is called gtar, but I don't use it so I don't know exact versioning.
+ FUnzip := 'unzip'; //unzip needed at least for FPC chm help
I still plan to continue creating CHMs for 2.6.2 next weekend (I can generate them again, but the quality sucks), and I can also generate .tar.gz from now on (or .bz2)
valid bunzip2: hopefully bunzip2 --help works on FreeBSD and returns status code 0. If not, the code will need to be changed with an {$IFDEF BSD} or FREEBSD
bzip2 and bunzip2 are in base, so even minimal systems installed have it.
-
FLastThreadId is defined as a Cardinal, but GetCurrentThreadID under FreeBSD returns a TThreadID type which is a pointer to record structure. Slightly different to Linux or Windows.
Attached is a patch which will fix the compilation problem.
In general in such case it is best to change it by simply using tthreadid everywhere for threadids, and define dummy types for Delphi if needed, and not to start random typecasting.
E.g. in this case on 64-bit systems, cardinal is still 32-bit, and the upper 32-bit of FreebSD threadids will be truncated.
-
Sorry for the delay.
I finally updated my compiler to FPC 2.6.2. I run the test app Tester/testGpStructuredStorage.lpi.
In the very first test, Storage Creation, it throws a SIGSEGV. While debugging I don't see any reason for it. I think it is related to Interface but you wrote it works for you with FPC 2.6.2.
I have a 64-bit Linux system. Could there be a bug in FPC related to Interfaces on 64-bit systems? Sounds weird.
function TForm1.TestGSSCreation: boolean;
var
storage: IGpStructuredStorage;
begin
Result := false;
Log('Testing storage creation');
try
DeleteFileUTF8(CStorageFile); { *Converted from DeleteFile* }
storage := CreateStorage;
storage.Initialize(CStorageFile, fmCreate); <-- it crashes here. I cannot enter Initialize method in debugger.
...
Juha
-
Modified fpcup for FreeBSD, NetBSD - no testing though. (posted to fpcup thread as well)
+ FTar := 'gnutar'; //check if available
The default tar is "tar". Since FreeBSD 8, it also supports some newer gnu commands like --strip FreeBSD7 is EOL since 2012-02-28 (but there is a 2.6.2 for it)
Try to use it as much as possible. GNU tar, if available is called gtar, but I don't use it so I don't know exact versioning.
Thanks, that's nice, will revert those changes again.
I still plan to continue creating CHMs for 2.6.2 next weekend (I can generate them again, but the quality sucks), and I can also generate .tar.gz from now on (or .bz2)
Thanks. Doesn't really affect fpcup... except perhaps the zip part...
Currently, fpcup downloads the chms from the Lazarus Sourceforge site:
http://sourceforge.net/projects/lazarus/files/Lazarus%20Documentation/Lazarus%201.0/fpc-lazarus-doc-chm-1.0.zip/download
Having .tar.gz or .tar.bz2 would be nice if zip isn't in base FreeBSD (I suspect it isn't). However, I check for zip being present and can kick out a warning to install a port/package.
That said ... having the 2.6.2 chms ready when Laz gets updated to use 2.6.2 would be good enough for me
valid bunzip2: hopefully bunzip2 --help works on FreeBSD and returns status code 0. If not, the code will need to be changed with an {$IFDEF BSD} or FREEBSD
bzip2 and bunzip2 are in base, so even minimal systems installed have it.
Great.
Looks like I'll have to download FreeBSD 9.1 soon and have a go...
-
In general in such case it is best to change it by simply using tthreadid everywhere for threadids, and define dummy types for Delphi if needed, and not to start random typecasting.
E.g. in this case on 64-bit systems, cardinal is still 32-bit, and the upper 32-bit of FreebSD threadids will be truncated.
That is why in my commits I changed this to ptruint instead of cardinal. As far as I understand this should be enough.
I'm going to start an freebsd vm tonight so more news tomorrow I guess.
-
That is why in my commits I changed this to ptruint instead of cardinal.
As far as I understand this should be enough.
I don't see a real problem, except that it is confusing, and is not optimal. (64-bits systems with 32-bit threadid lug the extra 4 bytes around,
debuggers show 64-bit numbers with a lot of zeroes etc)
I really don't see the problem of changing it to tthreadid
-
I really don't see the problem of changing it to tthreadid
I don't either and I probably will change it at the next commit if the component in question survives the conversion which is unlikely since it is not used from gpstructuredstorage component and I do not want to carry with me dead code.
-
freebsd is a pain to in my behind. pkg_add does not work, it cant find anything online and I do not know how to add more repositories to it even if I did I don't any repositories to add :'(.
Shitting here watching 3 consoles compiling my packages from source (ports works at least) is ahem narcotic. Narcolepsy is coming and I do not think I am ready for it yet.
-
I feel for you, taazz, looking at an x11 build screen myself ;)
(Oh and assuming you meant "sitting here" unless you have very strange hobbies :) )
-
Have installed PC-BSD and am fiddling with fpcup. Will report in fpcup thread if I get it working...
-
freebsd is a pain to in my behind. pkg_add does not work, it cant find anything online and I do not know how to add more repositories to it even if I did I don't any repositories to add :'(.
What other repositories? There is only the base ports tree.
Afaik in older versions you had to set some package root (like http://www.cyberciti.biz/tips/freebsd-changing-pkg_add-package-ftp-site-location.html ), something is preferable anyway if you have high
speed access (>1mbyte/s)
But in current versions it worked for me out of the box. Just a bit of pkg_add joe etc. Some packages have different names, but that is also the case between linux distros.
In case of doubt, looking in the All/ directory on ftp can help finding the right package name.
-
Well for me so far was hell on keyboard.
1st installation for some reason failed no buts or whys I had to delete the vm and start over.
then after the installation completed successfully this time I was introduced to the concept of ports that took some time to find the packages I want to install so I started big with kde4 doing pkg_add -r kde4/mc/joe etc will always fail with package not found on ftp://ftp.freebsd/....... so the next logical step was to make install the kde4 that started a multihour compile and install of various dependencies that required my attention all the time as each package will open a config screen now and then for me to choose options and when it hit qzeitgeist package all hell broke loose, 1st the installation stopped with one error spend more time searching for that elusive package that needed to uncheck gnutls options in order for it to compile correctly and then when qzeitgeist was cleaning up the installation a kernel panic was raised where an malloc call failed to return the size that was asked for, after that I got to play with fsck and manually linking a few dosen of lost disk links and then I had to re start it with the -y param for the rest what fun I had watching a 20GB disk got relinked for the next half an hour.
The good thing is that now kde4 installation finds the already installed packages and moves fast to the uninstalled ones. Although I would love to continue in a second console installing fpc 2.6.2 and testing fpcup that bigchimp just created for the BSD I am very worry that a second kernel panic (also known as out of memory) might hit me again so I'm just watching the kde4 compiling at the moment, fingers crossed, no more problems will be encountered.
Setting up a desktop on freebsd 9.1 is no piece of cake all night yesterday with nothing to show and of course after the correct installation of kde there is the minor issue of setting up the system to start on a kde login that will be more fun hunting down elusive .conf files to add an option or two which I'll forget in a weeks time again.
-
Well for me so far was hell on keyboard.
1st installation for some reason failed no buts or whys I had to delete the vm and start over.
then after the installation completed successfully this time I was introduced to the concept of ports that took some time to find the packages I want to install so I started big with kde4 doing pkg_add -r kde4/mc/joe etc will always fail with package not found on ftp://ftp.freebsd/....... so the next logical step was to make install the kde4 that started a multihour compile and install of various dependencies that required my attention all the time as each package will open a config screen now and then for me to choose options and when it hit qzeitgeist package all hell broke loose,
Strange, I do not recognize at all. Since the Linux distros went GUI and KMS, I generally had less trouble with FreeBSD then with Linux (since on Linux there are the occasional video card related problems during setup, specially in the last two years with the @$&@%$) gnome fallback stuff).
The last time I manually compiled anything, was when I got my Athlon64, which in itself says enough.
I don't usually fully dress up the desktop though, I usually just install windowmaker and let the basic install install X. Mostly that is because I don't care anyway. Though I have had gnome2 installs too. And I don't use VMs (actually I do, but I don't even have X configured in them, they are for FreeBSD release building only)
An option could be to use PCBSD, which is a freebsd spin which has a more newbie desktop-out-of-the-box concept.
-
so the next logical step was to make install the kde4 that started a multihour compile and install of various dependencies that required my attention all the time as each package will open a config screen now and then for me to choose options
Apparently make -DBATCH install clean is the magic incantation. That'll skip all questions and use defaults. No idea how that would deal with your zeitgeist woes though.
Myself, I downloaded PC-BSD and had working X (probably KDE) out of the box. Even getting Laz+FPC was easy by going through their software tool (did end up with an ancient 0.9.30 Laz). After installing mercurial (the same way), I got fpcup going...
-
for opensuse 12 installed relatively painless compared with freeBSD, although I do have a very old very compliant laptop (no 3D accelerator just an intel card) so I didn't expect any problems to begin with.
And Although it is not perfect (the desktop login screen is not I was expected) it was useable from the start and with the cnf and yast I was able to find my way around problems extremely fast.
I wouldn't bother to install a desktop as well but since this is going to be my only bsd based installation I though why not create an environment for testing my various components on it too (famous last words?).
in any case I haven't looked at your links yet but I'm going to need them after the kde4 finished installing I guess. thank you for posting them.
Apparently make -DBATCH install clean is the magic incantation. That'll skip all questions and use defaults. No idea how that would deal with your zeitgeist woes though.
Myself, I downloaded PC-BSD and had working X (probably KDE) out of the box. Even getting Laz+FPC was easy by going through their software tool (did end up with an ancient 0.9.30 Laz). After installing mercurial (the same way), I got fpcup going...
Lol I like that I'm going to start a new brunch (in the codelibrarian ) named linux incantations, there will be placed all such helpful diamonds of wisdom.
Let me add that I do not dare to stop the current installation process at the moment but will be using that gem a lot after that.
-
Apparently make -DBATCH install clean is the magic incantation. That'll skip all questions and use defaults. No idea how that would deal with your zeitgeist woes though.
Lol I like that I'm going to start a new brunch (in the codelibrarian ) named linux incantations, there will be placed all such helpful diamonds of wisdom.
;)
TBH, I didn't coin that phrase or come up with that snippet :)
-
freebsd is a pain to in my behind. pkg_add does not work, it cant find anything online and I do not know how to add more repositories to it even if I did I don't any repositories to add :'(.
There was a security issue with the repositories or something, just before they released 9.1 - so to be on the safe side, they decided to disable binary packages for that release. The ports collection works very well, and is dead easy to us. 'make install clean' is pretty much all you need to know. What is nice about ports, is that you can configure the apps (make config) before you build them, so you can have as little or as much functionality as you want.
I absolutely love FreeBSD! Also if you don't know how to do something, your first port of call should be the FreeBSD Handbook - it covers 99% of what most people need. Then try the FreeBSD Forums, if you still have question. The Handbook is up to date, very detailed with lots of example commands etc. Just brilliant.
-
want to install so I started big with kde4 doing pkg_add -r kde4/mc/joe etc will always fail with package not found on ftp://ftp.freebsd/.......
See my earlier reply.
so the next logical step was to make install the kde4 that started a multihour compile and install of various dependencies that required my attention all the time as each package will open a config screen now and then
Somebody didn't read the Handbook. :-) make config-recursive will allow you to configure all dependencies. Then make install clean will compile everything without interruptions.
Setting up a desktop on freebsd 9.1 is no piece of cake
The FreeBSD Hanbook (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html)) has a chapter on setting up X11. I followed it to the letter, an was up and running in minutes.
-
Put any arguments that you always want to use in /etc/make.conf btw.