[sldev] First shot at building source.

[Alan Grimes]

New business, late last night, before I colapsed on my keyboard, I
noticed that SL was defining a custom bool type. WTF??? bool has been a
part of C++ for more than ten years and has been back-ported into C as
of '99. Why define your own bool?!?!?! The only explaination I can think
of is that you wanted to garentee a specific word alignment... Even that
is pretty lame because there are other ways of doing that... (data
alignment is important, you know...)

Also, there is a stdint.h file on most platforms which will, according
to the standard, give you garenteed datatypes.

I'll have to review the supported platforms list but I'm sure that all
of them offer fairly good if not excelant implementations of these
standard routines....

I also noticed that you seemed to be using the "Apache Runtime Library"
to provie you with your threading routines. My own insticnct would be to
use SDL's thread library in order to maximize the exploitation of what
you already depend on. Is there a reason to justify this extra dependancy?

old business:

Callum Lerwick wrote:

>> 1. Including third party libraries with your distro is very bad karma.
>> It garentees that your stuff will rapidly become bloated and
>> unmaintainable. Many of the libraries in the current distribution can be
>> deleted and the client still runs against the host libraries with no
>> visible impact on performance.

> The third partly libraries are in an optional seperate tarball.

OK... But the stuff in the main tarball expects headers and library
paths to be in certain configurations.

>> 3. What's up with xmlrpc-epi? It seems to be a dead package... Why not
>> maintain it in house instead of applying 20 patches to the stuff on
>> sourceforge?

> Or port to xmlrpc-c, which seems a bit more lively and has wider use.

> http://xmlrpc-c.sourceforge.net/

I don't know much about that package at all... I can't even say whether
that is a better idea.

>> 6. What i really need is a multithreaded client. I have a 1.2ghz dual
>> athlon... Getting a bigger machine would be pointless if I can only use
>> 1 CPU. =(

> Rice. (It is multithreaded.)

What do you mean by "rice"?

Multithreading is certainly and emphatically not enabled on Linux. --
not in the current release version at least. =(((


>> 7. There seems to be some issues compiling against Nvidia's openGL
>> headers. I'd love to use DRI/Mesa but IT DOES NOT WORK. Seems to be a
>> glext call without including glext and enabling the prototypes...

> Mesa headers work fine. You don't have to nor should you compile against
> nvidia headers to use nvidia drivers.

[nvidia header compile problem]

> https://wiki.secondlife.com/wiki/Common_compilation_problems

Okay, there's an issue with compiling against Nvidia's headers...
Hmm... I guess I'll have to figure out what the underlying issue is.

I hope there's a workaround... I just got loaded with a major project at
work...

I'm going to spend the rest of tonite in-world... I'll try to get back
to the code over the weekend.

-- 
Opera: Sing it loud! :o(  )>-<