@Chris

Damn... That sucks

Is it possible to use -lauto when building a shared object? If so, how is the correct way to do so?

This is my shared object code:

*******
#include <proto/dos.h>

int printhello()
{
IDOS->Printf ("Hello world!\n");
return (0);
}
*********
and the main code:
*********
extern int printhello();

main()
{
printhello();
}
**********


and this is the makefile:

gcc -shared -Wl,--no-undefined myso.c -o libmyso.so -lauto
gcc -use-dynld -o mytest mymain.c -L. -lmyso -lauto


As you will see, the linker gives errors like "undefined reference to IDOS" etc.

I have tried without -Wl,--no-undefined, and it does seem to work this way. Only problem is, I need to keep this flag on for other reasons! Help!?

@spotUP

Since glib doesn't deal with graphics, I don't think it is relying on amicygnix. I use glib for Qt, and I can run qt console programs from Shell without amicygnix being even started. I think you should take a look at it.

Oh and by the way, I have just myself compiled a .so version, that you are free to use

@spotUP

As far as I recall, there is a gettext in the amicygnix archive.

EDIT: Yes there is. What is it supposed to do?...
EDIT: And of course there is a glib2.0 also in there!

@kas1e

Quote:

I think it's going to be very hard, but then again, I'm not the best programmer you could ask for. Actually I haven't looked very much inside Qt at all, I have just been patient enough to find the right configuration options to make it compile. Fx. just compiling the WebKit module takes more than 24 hourse etc. I think it would be pretty much impossible for someone like me to do a native port, sorry.

@Fab

Is vfork() enough? Because then I have some code, you might be able to use

@kas1e

As I also know nothing about Haiku (other than that it used to be BeOS, maybe ??), so I don't know if it will make sense to collaborate. I also know none of the applications that you mention, but I'll take a look at it and see if any of them make sense to port at the current stage. My personal goals are to have the Qt WebKit browser work and to try and make a port of MuseScore (music editing).



News on Qt: Moved the entire thing to dynamic linking (phew), so now instead of having executables of 70 MB they are now down to 2 MB or less On the downside every app now firmly crashes on exit...

Also WebKit module is now partially functional:

http://dl.dropbox.com/u/5482530/Images/webkit1.png

Only offline browsing is supported at the moment, though.

@Deniil

I have a SAM-flex, and I have the same problem


Quote:

I withdraw my statement, as I cannot produce this problem anymore here. Maybe an update 2 fix

@abalaban

I think you should take a look in SDK:include/include_h/exec/alerts.h

Although I don't know how to decifer it...

@thread:

1) I can confirm the endless recoverable alerts here

2) Can anyone confirm the multi-assign bug that I mentioned earlier? (Read prev. post).

@nbache

Thank Niels, you always seem to know what to d? ;). Still, i Think the user should somehow be alerted to the actions of the disc validator.

I don't think these have come up earlier:

1) When a mutli-assign is made during startup (for instance by MUI in the user-startup), and if there are files with the same filename in both directories, then boot will hang on the splash screen. I've had this happen multiple times, and I've had to remove the MUI assigns from user-startup alltogether. This is NOT very userfriendly at all.

2) The discdoctor (or whatever it is called nowadays)! When a program (for instance Quake 3) crashes in the middle of something with files open, then the disc will be unvalidated at reboot and the discdoctor will initiate at boot time. This might _also_ hang up the machine at the splash screen. Even worse, it might not even validate at all unless you reboot without startup-sequence and wait (often for a long time) for the discdoctor to finish. This has been a problem since old classic days, and I think it is time for the discdoctor to a) become verbose and tell the user, what is happening and b) for system boot to wait until the discdoctor finishes before continuing the boot process. Anything less is going to break the user experience.

@abalaban

I finally got around to reply

@DAX

and Google Earth... and Skype... and.... 8-D

@kas1e

...and _create_ many more new apps, hopefully

No seriously, if you are thinking of learning how to code apps, Qt is a really great environment. Of course you have to get your grips on c++, but then you get a really easy and diverse environment, and not to forget near instant portability 8-D

A native version is pretty far out in the future, though...

@kas1e

Thanks for the info

I'll see if I can use it, only rebuilding libQtGui takes almost half a day... :(

First screenshot of the Qt Designer running:

http://dl.dropbox.com/u/5482530/Images/designer.png

And yes, it _does_ work and doesn't crash (at least not yet!).

@Chris

I needed the static version, because Qt cannot build with -use-dynld at this time. Sadly.

There is a bug in elf.library, though, that makes dlopen() crash with my plugins.

@MickJT

Thanks. libdl seems to be exactly what I need!

I'm trying to expand plugin-capabilities of Qt, and
some code refers to dlopen()/dlclose()/dlsym(). The code links, but does not work.

Now I'm trying to make a small test-app that uses
dlopen, but it doesn't link, telling me "undefined reference to
dlopen".

I can't seem to find dlopen as symbol in any of the SDK libraries, so how come Qt links? If there is some macro definition somewhere, I can't find it. Help!