Forum > Windows
BOINC as library
Raistmer:
Well, as big fan of QNX OS I think the more modular app is the better as far as it doesnt impact performance ;) Another plus of dll'ed BOINC interface is shortened build times - devs certainly should like this idea ;)
Considering my build attemts, switching to Release32-NoGFX-xW options set brought bunch of compile errors (12 errors) in benchmark.cpp and cpu_x86.cpp. I have strong impression that Optimizer project just simulated compilation before (with no errors but no objs too). There are all objs from tis project now besides these two sourses that failed to compile.
Will investigate errors more closely then post.
P.S. after closer look only 3 errors remain (other originated from misplaced #endif, my fault). All belong to these lines of code ( cpu_x86.cpp).
case _INTEL:
cache.shared_L1_L2 = true;
bool hyper = testBit(1,edx_,28);
.\cpu_x86.cpp(143): error: invalid combination of type specifiers
hyper is defined as _int64 somewhere. So changing variable name solves this error (and remaining 2 too).
P.P.S. Well, now got position_history( 0 ),-related error too ::) After adding some missing #include statement and forcing const char* to char* conversions (hope it will not corrupt memory at run time %) ) it's the only remaining error.
Jason G:
--- Quote from: Raistmer on 27 Oct 2007, 06:03:50 pm ---Well, now got position_history( 0 ),-related error too .....
--- End quote ---
Yeah, I figured the cryptic message was saying there was no constructor of type position_history( int) .... and position_history seems to be a vector list or some such. Carefully commenting the '0' out seemed to let C++ use the default constructor, that 'seemed' to work for me.
I'm all for either explicitly using an existing correct constructor to initialise with though, or ,making a constructor of the right form if really needed .
Have fun, you're nearly there :D After a few weeks on and off, I'm still pretty mystified by a lot of it but baby steps and lots of silly questions seems to be clarifying a lot gradually.
Jason
Raistmer:
Yes, I commented it out too for a moment.
Now encounter some linker errors. Some of these originate from using evaluation version of IPP (so there are slightly different lib names). But remaining are much worse. For example,
linker cant find definition of parse_command_line function. There is declaration
extern int parse_command_line(char*, char**);
in str_util.h but... no definition was found in project sources. I hardly believe this function belongs to IPP. So where to find it's definition still open question ... :o
Jason G:
--- Quote from: Raistmer on 28 Oct 2007, 05:57:23 am ---.... So where to find it's definition still open question ... :o
--- End quote ---
Hmm, in mine that seems to be in Util.C , part of the libboinc solution. maybe your build order has that being compiled after set_boinc where it is called from main.cpp? or maybe util.H is not included [at top of main.cpp] for some reason?
[Ahhh, maybe libboinc directory is not added in 'Additional include directories? for seti_boinc soln]
Raistmer:
In my BOINC sources this function defined boinc\lib\in str_util.c. And this file doesnt included in project source tree. That's why I didnt find definition while conducting search in project files via VS. File search on entire directory via FAR was more successfull :)
Probably I should include this file in libboinc project in project tree.
(I use one of the latests BOINC sources, doesn't downloaded from this site)
P.S. Now only 3 unresolved links remains. Will search for another missing sources...
P.P.S. LoL :D Great definitions of missing links from boinc\api\static_graphics.C
void boinc_app_mouse_button(int x, int y, int which, int is_down) {
}
void boinc_app_mouse_move(int x, int y, int left, int middle, int right) {
}
Probably there should be // ToDo comment ;)
I added this file to libboincapi, but it doesn't compile - missing boinc_resolve_filename function declaration. It seems there are some differences in BOINC api that needed to be reflected in project tree.
P.P.P.S. After some modifications of project tree and adding some #include statements I got exe-file. Hope it pass validity tests ... (fingers crossed) :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version