Allegro.cc - Online Community

Allegro.cc Forums » Allegro Development » Allegro 5RPM

This thread is locked; no one can reply to it. rss feed Print
 1   2 
Allegro 5RPM
bamccaig
Member #7,536
July 2006
avatar

The descriptions seem correct.

Thank you. I've created a review request: https://bugzilla.redhat.com/show_bug.cgi?id=680205

I don't know that you should even include the allegro-main library. I think it's just an empty library on Linux.

You may be correct. IIRC, I was told in #allegro-dev that it should be used anyway for platform independent programs. :-/ I didn't actually bother to look inside it until now. It looks like it surely will be compiled down to practically nothing in Linux, but I guess at least the header files are still necessary to avoid warnings about them being missing. :-/ I wonder what, if anything, is even in the .so (and why it would be compiled at all in Linux)... :-X

Arthur Kalliokoski
Second in Command
February 2005
avatar

pepsi@fractalcmt:~ 01:48 PM $ ls /usr/local/lib/liballegro_main.so -l
lrwxrwxrwx 1 root root 22 2011-02-21 20:30 /usr/local/lib/liballegro_main.so -> liballegro_main.so.5.0
pepsi@fractalcmt:~ 01:49 PM $ ls /usr/local/lib/liballegro_main.so.5.0 -l
lrwxrwxrwx 1 root root 24 2011-02-21 16:45 /usr/local/lib/liballegro_main.so.5.0 -> liballegro_main.so.5.0.0
pepsi@fractalcmt:~ 01:49 PM $ ls /usr/local/lib/liballegro_main.so -l
lrwxrwxrwx 1 root root 22 2011-02-21 20:30 /usr/local/lib/liballegro_main.so -> liballegro_main.so.5.0
pepsi@fractalcmt:~ 01:49 PM $ ls /usr/local/lib/liballegro_main.so.5.0 -l
lrwxrwxrwx 1 root root 24 2011-02-21 16:45 /usr/local/lib/liballegro_main.so.5.0 -> liballegro_main.so.5.0.0
pepsi@fractalcmt:~ 01:49 PM $ ls /usr/local/lib/liballegro_main.so.5.0.0 -l
-rwxr-xr-x 1 root root 4074 2011-02-21 20:29 /usr/local/lib/liballegro_main.so.5.0.0
pepsi@fractalcmt:~ 01:49 PM $ nm /usr/local/lib/liballegro_main.so.5.0.0
000014dc a _DYNAMIC
00001628 a GLOBAL_OFFSET_TABLE
         w _Jv_RegisterClasses
000014cc d _CTOR_END_
000014c8 d _CTOR_LIST_
000014d4 d _DTOR_END_
000014d0 d _DTOR_LIST_
000004c4 r _FRAME_END_
000014d8 d _JCR_END_
000014d8 d _JCR_LIST_
00001640 A __bss_start
         w __cxa_finalize@@GLIBC_2.1.3
00000470 t __do_global_ctors_aux
000003b0 t __do_global_dtors_aux
0000163c d __dso_handle
         w _gmon_start_
00000467 t __i686.get_pc_thunk.bx
00001640 A _edata
00001648 A _end
000004a8 T _fini
00000348 T _init
00001640 b completed.5936
00001644 b dtor_idx.5938
00000430 t frame_dummy

“Throughout history, poverty is the normal condition of man. Advances which permit this norm to be exceeded — here and there, now and then — are the work of an extremely small minority, frequently despised, often condemned, and almost always opposed by all right-thinking people. Whenever this tiny minority is kept from creating, or (as sometimes happens) is driven out of a society, the people then slip back into abject poverty. This is known as "bad luck.”

― Robert A. Heinlein

bamccaig
Member #7,536
July 2006
avatar

Now that I actually look at the package contents, there's really nothing in the main addon packages at all... There's only the empty (for all intents and purposes) shared object file and its symlinks, and the useless (for all intents and purposes) .pc file... Not even a header file. Then again, perhaps the developers wanted for UNIX build systems to be able to still link to this shared object library (which does nothing) so that users don't need special OS X build rules? It looks like Linux-wise I could get rid of the main addon altogether, but perhaps the Allegro developers want it distributed anyway? Well? :P

Thomas Fjellstrom
Member #476
June 2000
avatar

Thats pretty much it. This way you don't have to special case linking. You can just link to allegro and allegro_main and call it a day.

--
Thomas Fjellstrom - [website] - [email] - [Allegro Wiki] - [Allegro TODO]
"If you can't think of a better solution, don't try to make a better solution." -- weapon_S
"The less evidence we have for what we believe is certain, the more violently we defend beliefs against those who don't agree" -- https://twitter.com/neiltyson/status/592870205409353730

Evert
Member #794
November 2000
avatar

bamccaig said:

Then again, perhaps the developers wanted for UNIX build systems to be able to still link to this shared object library (which does nothing) so that users don't need special OS X build rules? It looks like Linux-wise I could get rid of the main addon altogether, but perhaps the Allegro developers want it distributed anyway?

Basically this, yes.
With allegro-main included in the linker options (through pkg-config), the same code compiles, with the exact same Makefile, on any flavour of UNIX, including Linux and Mac OS X.

Peter Wang
Member #23
April 2000

You might want to place allegro_main in the main allegro package.

bamccaig
Member #7,536
July 2006
avatar

You might want to place allegro_main in the main allegro package.

The allegro package maintainer (who is going to be sponsoring me if all works out) actually suggested that I merge most of the addons (basically any that don't pull in extra dependencies) into the main package. :) So no worries. That will be addressed shortly. Thanks for the help.

 1   2 


Go to: