C/C++ Development in Puppy Linux

[SirDuncan]

Because of it's extent, the pet-installation seems not to be the best solution for a fast and problem-free use of Anjuta. But there should be a choice for those that wish a professional development environment. Therefor I want to:
Melt the C-development-file devx_400.sfs with Anjuta to devx_anjuta_400.sfs.
On my part: Not much experience how proceed. Help very welcome!

Yes, I think a development sqashfile with devx and Anjuta would be the way to go. The only problem is that it would require a different squashfile for every version of Puppy you want to support.

@ BarryK
Enveria seems to be continued on a commercial base:
http://www.kaizendenki.com/
So it's maybe not the best choice for Puppy. But I am also still searching a light weight IDE useful to develop small applications fast that can make it into Puppy or devx_xxx.sfs directly. Was someone successful in this direction?

According to the Enveria documentation (I've been looking into it since I read Bary's post), that was the company that the program's creator was interning with when he made it. It appears that they have taken up development and are planning to market it. If they have rights to it, they can make it closed source now, but the old code is still GPL and can be expanded upon if the community wishes to do so. If the creator maintained rights to the program, then all development done by the company will have to be released under the GPL regardless of what support packages they are selling. Either way, I see no reason for us not to use it if it works well.

EDIT: After reading a little bit further into the creator's project report, I'm pretty sure that the company owns the rights to the program. Still, the GPL code is available for us to use if we want to.

It also seems that the company started the program before this student went to work there, and that they made the decision to open source it. This means that there is a good chance that it will remain open source. I will be trying to get it working once I finish this week's class programming project.

[muggins]

With the need to upgrade the gtk version, to get anjuta working, how compatible will any binaries produced be with pupversions that don't have that gtk verion?

Is little puppy destined to turn into a St. Bernard?

[prach]

Hi Wosh, Can you write how to compile Anjuta 2.4.1 on Puppy 4.00 ?
i want to use its create my customize puppy include anjuta.

[Lobster]

I created a Linux Tmxxine for programmers but think I was overly ambitious and not happy with the results
http://tmxxine.com/wik/wikka.php?wakka= ... xinePhoton

. . . however there is considerable mileage in a .pet, sfs
for Puppy for c/c++ that includes an IDE
thus bringing it a step up from Geany which supports colour coding

be aware of this thread too - the developer is very friendly
http://www.murga-linux.com/puppy/viewto ... 280#186280

[BarryK]

Yes, they are asking US 99.95 for Enveria:
http://www.kaizendenki.com/kd/enveria_rad_ide.php

No reason why we can't work on the GPL version though. It probably just has trivial bugs, but they aren't interested in fixing it, for obvious reasons.

Wosh, yes, an SFS file is best. But name it as something like 'anjuta-puppy-4.x.sfs' to show that it will work in all the Puppy4 series.
If you only have '_400' then the boot scripts will only allow it to be loadedfor that version of Puppy. Any SFS file with that specific string in it, exactly like '_400' or '_301' will only be usable with that version of Puppy.
But, you use anything else, like with a dot in it, or without the underscore: '-4.0' then any Puppy can use it. But I suggest put something like 'puppy-4.x' in the name as that helps people to identify that the sfs is designed for Puppy4.

If you can get everything into a single directory, named say 'anjuta-puppy-4.x' then MU has created a nice script 'dir2sfs' to make it easy to create a sfs file, although it's pretty easy to use mksquashfs directly.

I suppose you don't really need the string 'puppy' in the sfs name. That was just an example.

[tmpMichigan]

I compiled Code::Blocks v.8.02 and wxGTK v.2.8.7 from source the day 4.00 was officially released and it has been working fine. I can try making a sfs file if there is interest - just let me know. I was just about to try setting up cross-compiling for win32...for those of us who dwell in both worlds, it's nice to have the same IDE in both.

I would have posted sooner, but I've never visited the forum - I stumbled upon a link to this discussion in Barry's blog.

- Thanks

[Lobster]

I can try making a sfs file if there is interest - just let me know.

Please do.

[tmpMichigan]

It took 3 hours, but everything was isolated on the first attempt. My hat is off to those who visioned and brought to the life this "file layering/trumping" method - very nice. I thought making a SFS might be challenging, but it's just an elegant and simple design with which to work.

To test, I booted Puppy with a new/clean 2fs, loaded the new cb_400.sfs and devx_400.sfs (named to ensure devx has priority...), created a template GTK project, and built/ran successfully without any other configuration. I don't believe there will be issues, but please let me know if anyone experiences any. Note: it may be a few days until I check this forum again.

I don't have a place to host it, so I uploaded to mediafire. The file is 26MB:
http://www.mediafire.com/?nvxrygy11oj

md5:
678e6c77cd4a398c8a45aef92bc46934 cb_400.sfs

- Thanks

[Lobster]

Excellent.
Works.

I am off to write a Puppy blog entry about it . . .
http://www.puppylinux.org/community/blo ... ic-penguin

[Wosh]

@ muggins

Wosh wrote:
But there should be a choice for those that wish a professional development environment.

With the options of modularisation like the creation of sfs-files Puppy Linux will stay Chihuahua but it will have the strength of a St. Berhard.

@ tmpMichigan and others
Please go on building testing and providing a wide range of IDEs. Every IDE running in Puppy Linux will encourage more people to write good solutions for Puppy Linux.

@ all
I have spent some more time to test Anjuta and except of some bugs described below it seems to run rather smoothly. But due to it's pure size I haven't been able to test all functions.

I have time problems because I only can work for Puppy in my spare free time. So you have the options to wait until I can go on or to help me fixing the problems. For those who want to get on the project I have put together some files:
Anjuta Build History in PHISTORY
Anjuta Build Instructions in AnjutaBuildProcedure.html

The HTML-File is easy to use because all needed package-URLs are included. The packages can be downloaded directly with your browser. This together with my hints should enable you to build your own Anjuta within a few hours and maybe you will be able to help fixing the bugs.

You even should be able to build Anjuta for older Puppy-versions but then there will be even more dependencies and packages needed. The way to proceed should be similar to PHISTORY.

Bugs found:
I have fixed a bug that crashed Anjuta if the Valgrind plugin was active by updating from Gtk+2.10.0 in Puppy 4.00 to Gtk+2.12.9, but there are still some bugs to fix which still prevent me to create a sfs-file.

Bugs open:
1. The GtkSourceView-Plugin makes Anjuta crash if a file is loaded with GtkSourceView.
2. The help documentation is not found and a hint is displayed to download it from anjuta.org
3. The urls within the help open a warning-box instead of the corresponding web-site.

Reedited Start
June 5 2008
The old Anjuta 2.4.1 build procedure created a buggy Anjuta IDE. I have replaced it with the bug free Anjuta 2.4.2 build procedure. It will take you about 4 hours to build anjuta from the scratch.
Reedited End

[Caneri]

Hi all,

If anyone on this thread needs server space and bandwidth to publish their work on C++ pm me and I'll set you up with an ftp account so you will be able to keep up to date files available to the public.

Best,
Eric

[SirDuncan]

I have heard good things about Code Blocks. I think I may give it a try.

On the topic of Enveria, I got it compiled, but it looks kind of rough. The first thing I noticed was that the makefile was missing a few basic things like "make install". Once I had it running, I had trouble finding all of the controls because they were in separate windows. I couldn't see the two windows with the controls, because they were hidden behind the main window. It wasn't until I looked at the taskbar that I realized that they were there. The windows are not resizeable (well, they are, but nothing scales, you just get a bunch of empty or you hide half the objects in the window). The screenshot you see below was taken at 1024x768. In order to really use this, you would need a higher screen resolution than that.

If anyone wants to play with it, I'll post it, but I don't think it's worth using just yet.

[Wosh]

@ tmpMichigan

I was just about to try setting up cross-compiling for win32...for those of us who dwell in both worlds, it's nice to have the same IDE in both.

I for myself would appreciate to have an option to cross-compile projects.

I have made a short test with the CodeBlocks-IDE. Even if it is not that extensive like Anjuta it looks very promising.
It is quite easy to create the console project example and the GTK+ project example. Both compiled and ran well.

But also found a bug:
CodeBlocks freezes after the starting debugger has opened it's log console window. It only reacts after the console has been closed and then even debugging is possible. Because I didn't find information about the source packages used in your package I was not able to investigate deeper.
Therefore I suggest:

@ all
Every package provided for Puppy Linux should contain a package-build-file named BuildPuppyvvvPackagename-v.v.v.html
e.g. BuildPuppy400CodeBlocks-8.0.2.html that contains these informations:

1. Prerequisites to build the package
2. Description how the source-packages were installed
3. Source-package versions used
4. Download-URLs of the source-packages
5. Dependencies
6. Information about decisions taken, obstacles, bugs

I have chosen the HTML format because it can be edited easily with Puppy's preinstalled HTML-Editor and the packages can be downloaded directly by selecting them. An example what I am thinking about can be found in the file AnjutaBuildProcedure.html within my last reply.
Even if it may seem to be annoying to write such a file, the advantages prevail:

1. It can be reenacted how the package was build (even the creator will forget it after a while).
2. Next time the creation of the package will be a lot faster.
3. Bug tracking is made easier.
4. The creation of other (newer) versions of the package is done with little effort.
5. The package can be adapted to other versions Puppy Linux.
6. Different subsets of the package (light, extensive) can be created.

@ Caneri
I would appreciate to have place for up/downloading packages build by users. It should have an intuitive path structure that separates the test versions from the stable ones like:
Languages/C/IDEs/Anjuta/2.4.1/stable
Languages/C/IDEs/Anjuta/2.4.1/instable

or:
stable/Languages/C/IDEs/Anjuta/2.4.1
instable/Languages/C/IDEs/Anjuta/2.4.1

Every package directory should contain a README.TXT file informing the Puppy users about the prerequisites of the package.
If you have a similar conception about this topic we should PM.

PS
@ all
During the building of Anjuta it took me quite a long time to find out which library/package versions are installed in Puppy 4.00. Is there a file or web site that provides this information?

[MU]

During the building of Anjuta it took me quite a long time to find out which library/package versions are installed in Puppy 4.00. Is there a file or web site that provides this information?

Often you find this info in /usr/lib/pkgconfig/

These files contain version-infos.
Mark

[kirk]

Enveria seems to be continued on a commercial base:
http://www.kaizendenki.com/
So it's maybe not the best choice for Puppy. But I am also still searching a light weight IDE useful to develop small applications fast that can make it into Puppy or devx_xxx.sfs directly. Was someone successful in this direction?

It looks like it may be the other way around. First commercial then GPL.

See:

http://www.gnomefiles.com/app.php/Enver ... evelopment

[MU]

I don't have a place to host it, so I uploaded to mediafire. The file is 26MB:
http://www.mediafire.com/?nvxrygy11oj

md5:
678e6c77cd4a398c8a45aef92bc46934 cb_400.sfs

Mirror:
http://puppyisos.org/files/sfs/Puppy-4/

See here for the access-password:
http://www.murga-linux.com/puppy/viewtopic.php?t=28930

Mark

[muggins]

Here's a small ide...unfortunately not much information...not sure of current status:

http://lxrad.sourceforge.net/phpmysb-0. ... index.html

[BarryK]

muggins, you're a champ! That's a great discovery. See my blog post, and PET's to download:

http://puppylinux.com/blog/?viewDetailed=00114

[Viking Sailor]

Berry,

Here is another site with more info on LXRAD including the author's name and email.

http://freshmeat.net/projects/lxrad/

Paul

[kirk]

Here's another IDE that was posted on the forum:

http://www.murga-linux.com/puppy/viewto ... 4&start=15


It's less than 4MB uncompressed without the docs (which are about 8MB and look very nice ) and is cross platform.