C/C++ Development in Puppy Linux

Message

Caneri · #41 Post by **Caneri** » Thu 15 May 2008, 15:43

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 · #42 Post by **SirDuncan** » Thu 15 May 2008, 17:24

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 · #43 Post by **Wosh** » Fri 16 May 2008, 16:32

@ tmpMichigan

tmpMichigan wrote: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?

#44 Post by MU » Fri 16 May 2008, 17:11

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 · #45 Post by **kirk** » Sat 17 May 2008, 02:30

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

#46 Post by MU » Sat 17 May 2008, 17:54

tmpMichigan wrote: 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 · #47 Post by **muggins** » Thu 22 May 2008, 11:07

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

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

BarryK · #48 Post by **BarryK** » Fri 23 May 2008, 09:48

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 · #49 Post by **Viking Sailor** » Fri 23 May 2008, 10:19

Berry,

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

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

Paul

kirk · #50 Post by **kirk** » Fri 23 May 2008, 15:22

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.

boscobearbank · #51 Post by **boscobearbank** » Sat 24 May 2008, 00:54

Lastly, you might be interested in checking out JohnMurga's MurgaLua. While it's also based on an interpeted language, (Lua), it has bindings to the fltk toolkit, and it's also easy to interface lua with c/c++.

Guess I'm a few daysd behind in this discussion, but there's also Wolfgang Oertl's Lua-Gtk, which, very conveniently, has bindings to gtk2. I am not a Lua programmer, but I did manage to port one of my geologic modeling programs from C to (C++, Perl, Python, and) Lua-Gtk.

Wosh · #52 Post by **Wosh** » Tue 03 Jun 2008, 15:36

@ All Puppy Developers

I have fixed the Anjuta bugs and created an Anjuta-SFS file. But there is still one problem that prevents it's release. In current Puppy 4.00 anjuta-2.4.2-p400.sfs is mounted before pup_400.sfs.

Anjuta depends on a lot of library-versions from glib to gtk+ that have not made it into Puppy yet. So it is necessary to mount Anjuta as last SFS-File to activate the new library versions. I have searched /etc to find out where pup_400.sfs and the other sfs-files are mounted. No clue. Help neded.

The alternative would be to build pets from all new libraries and install them first. Very cumbersome!

raffy · #53 Post by **raffy** » Tue 03 Jun 2008, 23:47

Are sfs files mounted alphabetically? But I guess that does not count the pup_xxx.sfs. The process can be verified from /initrd/sbin/init (this is in 2.13).

Wosh · #54 Post by **Wosh** » Wed 04 Jun 2008, 06:01

@ raffy
In Puppy 400 init is a link to busybox in /initrd/pup_ro2/sbin. Does it really mount the sfs-files?

The sfs-files really are mounted in reverse alphabetical order.
To ensure anjuta to be mounted last I maybe should rename it aaaaaaaaanjuta-2.4.2-p400.sfs.

But pup_xxx.sfs is always mounted at last.

@ all
The sfs load order needs a fix. My suggestion is to take the boot manager order selected by the user. The boot manager also should include a non removable pup_xxx.sfs that only can be moved up down within the sfs load order. So my problem could be solved easily. But these are dreams of the future.

The problem could be solved more smartly by another solution I am thinking about But it would need support of the Puppy-Linux core team. I call it

Pupdater

Pupdater creates an updated pup_xxx.sfs with the newest version of packages loaded from a repository that holds updated package versions uploaded by trusted puppy developers.

In my case I would have uploaded all updated versions, run pupdater to create an updated pup_xxx.sfs. That's it. No need to change the boot order.
How about that?

PS
I thought I little bit deeper about pupdater. It also could be a good tool to create user adapted puppies without the need to rebuild Puppy via unleashed. No more derivatives needed. Hi folks, have you already thought what you would do with your obtained leisure time?

raffy · #55 Post by **raffy** » Wed 04 Jun 2008, 09:30

Maybe this new sfs issue needs its own thread?

Coilean · #56 Post by **Coilean** » Thu 05 Jun 2008, 18:14

I'm way out of my depth here, but I reckon it;'s the best way to learn.
I'm a puppy user for a couple of hours, and linux for only a little bit longer, so bear with me. I'm trying hard to break free from windows......

I' started on woshs anjuta procedure to install, but fell at the first hurdle.
I downloaded the libxml package and got errors on the make command

I don't know how to cut and paste from the command prompt, but i'm getting an error along the lines of 'automake-1.10 is missing on your system' and missing --run autoconf aclocal.m4:14

Any suggestions on how to continue?

Wosh · #57 Post by **Wosh** » Thu 05 Jun 2008, 21:50

@ Coilean

Please do not use the old Anjuta 2.4.1 build procedure any more. It 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.

If you can't expect the SFS-File release you can download it from:
http://www.murga-linux.com/puppy/viewto ... 9c627bd7b1

Just for you I have added a description how to activate the development package.

Cheers

L'Elfe · #58 Post by **L'Elfe** » Fri 17 Oct 2008, 11:16

Helo

I have installed code blocks on puppy 400 it's working , but i have this strange message when compiling and runing a simple console "hello world" into the EDI waht does that mean ? :

/usr/local/bin/cb_console_runner: /usr/lib/libstdc++.so.6: no version information available (required by /usr/local/bin/cb_console_runner)
/usr/local/bin/cb_console_runner: /usr/lib/libstdc++.so.6: no version information available (required by /usr/local/bin/cb_console_runner)
Hello world!
Press ENTER to continue.

Thanks

BarryK · #59 Post by **BarryK** » Fri 17 Oct 2008, 23:09

L'Elfe wrote:Helo

I have installed code blocks on puppy 400 it's working , but i have this strange message when compiling and runing a simple console "hello world" into the EDI waht does that mean ? :

/usr/local/bin/cb_console_runner: /usr/lib/libstdc++.so.6: no version information available (required by /usr/local/bin/cb_console_runner)
/usr/local/bin/cb_console_runner: /usr/lib/libstdc++.so.6: no version information available (required by /usr/local/bin/cb_console_runner)
Hello world!
Press ENTER to continue.

Thanks

You get this if the program was compiled for a different version of libstdc++.so. I presume that you must have used binary packages of code blocks and/or wxwidgets, rather than compiling it all in Puppy from source.

L'Elfe · #60 Post by **L'Elfe** » Mon 20 Oct 2008, 07:53

Yes i downloaded the cb_400.sfs done by tmpMichigan , and the link given by Mu in the previous page.

do you have a version for the devx_400.sfs ? that works better ?

is it difficult to compile codeblocks in puppy , i am a newbie in linux ?

Thanks

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

C/C++ Development in Puppy Linux

Every Package should contain a Package-Build-File

Re: C::B

LXRAD Info

Anjuta-2.4.2 SFS-File

alphabetical

Random SFS Mount Order in Puppy Linux

another thread

Anjuta 2.4.2 Build Procedure is bug free