Re: [bme-develop] Final BeMSN Release Progress

[Sir M. <obe...@ho...>]

Hi Jixt,

>I've tried to compile the bme stuff and I am stuck @ 41 errors. What I want 
>to say is that it is important to clean up the CVS. Also make sure 
>everything compiles before you do a check-in into the CVS. For people who 
>just want to make a build from the current CVS, it is a problem. You need 
>the sources of cryptlib(had to find it myself. i could not find it on the 
>homepage...). And you need to figure out why it does not compile.
>>Could anyone help me what I need to do(a preparation) before I compile the 
>>whole stuff? Maybe it would be nice to put that all on the homepage. I 
>>know developpers don't like documentation, but somethimes it is needed to 
>>speed up the development of your project ;)
>
I think documentation is very important! I tried to give a download and 
compile manual at bme.sourceforge.net but it's slightly outdated now...page 
should have an update anyway!

about compiling: first to make sure: you are using Bme_x86.proj right? make 
sure you place the cryplib.h file in a dir accessible to BeIDE(not sure 
which dir, maybe the others can help here).  I wonder when you downloaded 
the code from CVS? The Netwatch files weren't in cvs before, but Simon 
uploaded them to cvs this week(right Simon?), if it doesn't compile, and you 
don't have them, just delete the entire Netwatch dir to fix the compiling 
issues. Another issue is the libbnetapi.so file, this is a BONE file...the 
r5 file is called libnetapi.so: this doesn't cause any compiling issues but 
make sure you have included the right one in your project, otherwise you 
won't get connected to internet.

Another issue MYOB pointed out to me was that the Bme app only compiles 
correctly(without causing a crash) on Dano, when debugging is enabled...not 
sure why!  hope this helps! otherwise we should sometime talk in BeShare 
about this!

>What I also think is that it would be bad to create another module 
>specially for the final release. All should be @ one place, otherwise it 
>will become confusing.
>
I agree...as I've understood from Simon, the old BeMSN files will still be 
in the attic, maybe the thing we could do is set a package with the latest 
release (binary + source) on our homepage,  just to have them around!

regards,

Tim

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963