Tiny Core Extensions > TCE 1.x

fltk-fluid

<< < (2/3) > >>

roberts:
I just tried the latest compiletc and everything works! The fltk 'stuff' is in /usr/lib/libfltk*
calling g++ directly, using a Makefile, or using fltk-config all worked fine.

Using the above fltk-fluid also works and will write the .cxx and c.h files to use with the above.
By default these two tools are not integrated, but you can setup fluid to call g++, a script, etc.

MikeLockmoore:
Hmm.  I do have files matching /usr/lib/libfltk*, but I don't seem to have a fltk-config executable or script anyplace.  I thought I might need to reload my compiletc.tce, but when I tried to load the tci-unload.tce (or was that tce-uninstall.tce?), it stalled out, and when I tried to move the wget window a bit, I saw some error message related to ssl.  (Sorry I didn't grab the actual message, but I tried a reboot).  Now, I can't even get a successful connect to the TCE repository.  ("Error trying to connect.  Try later.")  :-\

When I listed (tar -tf) out the contents of my compiletc.tce in my PPI repository under /mnt, among lots of stuff, I do see libfl.a.  My compiletc.tce does have a lot of /usr/inc/FL/ header files.  But I don't see the libfltk.so.1.1 file or some others like that that are in my /usr/lib directly.  Also, I don't see any files containing fltk, so are fltk-config and some of those other libfl* files created by an installation script, which maybe did not succeed for me when I installed compiletc.tce?  I guess I'm missing some piece of info to understand and fix my problem.  Thanks for any further help.

roberts:
fltk-config is in /usr/bin

compiletc.tce is not PPI compatible (loads/installs entirely under /usr/local) , so I am confused by your statment that compiletc.tce is in PPI?

Perhaps it would be helpful to post the contents of the command showbootcodes so that we may know which mode of TC you are using.

MikeLockmoore:
Robert, thanks for taking time to consider my problems.  The command showbootcodes returns:

    tce=hdc4

hdc4 is a fourth partition of my laptop harddisk.  I'm not sure why TC has defined it as hdc instead of hda, but TC boots and runs OK from it this way.  hdc4 is an ex2 partition that hosts another distro of Linux and my backup/restore data, so its a "frugal" installation, yes?  hdc3 is a swap partition that TC seems willing to use, but my mem stats don't show any swap actually used .  Anyway, I think this tce=hdc4 boot parameter makes it PPI mode, right?

Here is my output from mount:

--- Code: ---rootfs on / type rootfs (rw)
/proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,mode=600)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hdc4 on /mnt/hdc4 type ext2 (rw,nosuid,nodev,relatime,errors=continue)

--- End code ---

My /tmp/stats.txt file contains:

--- Code: ---atk
cairo
compiletc
expat2
file
filesystems-2.6.26
flash9
fontconfig
gcc-3.3.6
geany
getFlash9
glib2
graphics-libs-1
gtk2
libglade
libxml2
linux-headers-2.6.26
ndiswrapper_full
opera
OSS
pango
perl5
pixman
rox-filer
shared-mime-info
wget
wireless-2.6.26
wireless_tools
Xlibs_support

--- End code ---

If compiletc.tce is not compatible with my boot mode, then perhaps it only partially installed.  I did not know that it may not work like this.  I appologize if I overlooked this in the appbrowser info, or otherwise misunderstood the operational modes of TC.  I guess the compiletc.tce install seemed to work OK because I was able to compile the acx wireless open source driver and do a few other things successfully with the standard gcc and make.

By the way, I am still getting errors trying to Connect | TCE in the appbrowser and not sure how to go about fixing that.  EDIT:  I launched appbrowser from the command-line, and I see this message:

--- Code: ---wget: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
--- End code ---
What's the best way to fix this?

I'm a professional developer with a lot of Win32 and system-level (embedded) Linux experience, and some GTK experience.  I think I could pick up FLTK development pretty easily and contribute a few things along the way, but I seem to be tripped up on a few of these basic setup and installation issues right now.  But if you (Robert, or others) invest a few minutes with me, I hope you see it pay back many-fold soon!   ;)
--
Mike L.

Jason W:
Hi Mike,
I see that wget is installed without openssl-0.9.8h.  You could rename /usr/local/bin/wget to something else and you should be able to use the appbrowser again.  Install openssl and then rename /usr/local/bin/wget back to it's original and that issue should be solved.

Navigation

[0] Message Index

[#] Next page

[*] Previous page