Thread: [bme-develop] Fw: Issues with project files

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Guys,

MYOB sent me.

I replied to most of it. I agree with his comments about project
files though, they could do with reorganising.

I've told him to use the other project file, should fix his
compile issues.

-------Forwarded mail below---------------
Simon

Theres some serious problems with Bme's BeIDE project files. One
of 
them is speed - searching all of /boot/home/config/lib causes
biiiig 
problems if you have all of VLC's build tools and Python
installed. Not 
that thats a problem, just an "issue". This can be solved by
making 
people symlink cryptib into the /boot/develop/lib/x86 folder and
removing the /boot/home/config/lib access path

Also, most of the system libraries are included wrong. They
should not 
be included from /boot/beos/system/lib, they should be included
from /
boot/develop/lib, and with the correct architechture first (x86/
or ppc
/).

Also, the path to the cryptlib header isn't in the file, and it 
probably should be included as <cryptlib/cryptlib.h> and not
just as 
cryptlib.h.

Also, it might not be a good idea to have the Net*.cpp files in
the 
project file, as they're not in CVS...

Another suggestion might be to have a BONE project file - you're
not 
meant to like to libnetapi.so on BONE, it should be libbnetapi. 
Although under OpenBeOS they'll probably just one file with the
other 
symlinked...

You also don't need to add the headers to a project file. It
might 
speed up coding a little, but you can always get to the headers
by 
right-clicking the little arrow to the side of the file that
includes 
the header. Not having the header minorly speeds up the opening
parse 
time.

For purely asthetic regions, I'd move Bme.rsrc up the libraries.
Its 
another linktime item, so its logical there

All this is based off using "BeMSN.proj". This seemed like the
right 
choice of project file, having three is a liitle confusing :-)

None of this is meant to be critical mind, you're doing a great
job 
with Bme. I'm still looking into a ppc port BTW :-) Although I
do have 
more pressing issues (getting sound to work on my laptop, etc)
to deal 
with first. Although my PPC box is my most unadulterated system 
(running a horrible hyrbid R5 BONE/Dano/OBOS R1 mash up here),
so its 
the only box I have that makes R5 compatible builds :-)

I'm also interested in how the Hotmail integration is going to
work - 
I've written this before even compiling Bme or looking at the
code. 
Considering NetPositive doesn't do JScript, and Mozilla/Firefox
still 
has the "first-window-doesn't-show-requested-page" when running
as 
native browser, I'm very interested in how an app can use
Hotmail 
easily

As goes webcam and voice chat support, this is an area I'm
interested 
in, as I have a large number of friends overseas who seem to
assume MSN 
is the defacto standard for video and audio conferencing. To
confirm 
what one of the dev team said in the TBJ interview - yes,
supported 
webcams (CPIA parellel ones) do work as media nodes in exactly
the same 
was a capture card with a TV camera on it does. Unfortunately my
CPIA 
camera bit the dust a long time ago and my USB one is, clearly, 
unsupported. Also R5's USB kit just *does not* have the kit
required 
for USB webcams. So when OBOS R1 is out, contact me and bug me
over 
webcam support :-)

Cian / Kian "MYOB" Duffy

PS: Just compiling now, the code doesn't like BONE 7A here. Or
it could 
be my headers. But all the BNetEndpoint stuff doesn't compile, 
MsnList.cpp has casting issues, and IconHandle.cpp has
prototyping 
issues. Some of this could be down to my hacking around with the
project file though :-)
________________________________
15 Mbytes Free Web-based and  POP3
Sign up now: http://www.gawab.com