Shane Reilly wrote, On 26.05.2010 17:07 Uhr:
> Compiling it with MSYS worked without problems.
>
> Is there any way to update the documentation to mention your suggestion 
> <http://boinc.berkeley.edu/trac/wiki/CompileApp>?
> The statement under the MinGW Compilation heading reads, "To build the 
> boinc library and API for Windows using MinGW on Cygwin or 
> cross-compiling, you can use lib/Makefile.mingw." led me to believe that 
> I should not use the MSYS interface even though I had it installed. I 
> think it meant to read "...using MinGW on MSYS or cross-compiling..."
>   

The lib/Makefile.mingw was originally developed and is in use for 
cross-compiling Windows Apps on Linux.

I found it working on Cygwin, too (to build Apps for plain Windows, not 
for Cygwin - use the autoconf stuff to build a native Cygwin App & 
Client). I always wanted to try MSYS, but never found the time.

I'll add MSYS.

Best,
Bernd

> On 5/25/2010 3:43 PM, Nx Hien wrote:
>   
>> Don't try to use Cygwin to compile BOINC, try Msys+mingw instead.
>>
>> In the past I tried to compile it on Cygwin, but then I ended up 
>> changing too much BOINC's source code and decided to stop.
>>
>> ------------------------------------------------------------------------
>> *From:* Shane Reilly <[email protected]>
>> *To:* Nx Hien <[email protected]>
>> *Sent:* Tue, May 25, 2010 2:37:33 PM
>> *Subject:* Re: [boinc_dev] Compilation Documentation - DevC++
>>
>> I am using the Cygwin interface.
>> Typing ./_autosetup gives errors, I think I need to install something 
>> in the Cygwin setup for shell scripts to work:
>>
>> $ ./_autosetup
>> ./_autosetup: line 2: $'\r': command not found
>> ./_autosetup: line 4: $'\r': command not found
>> ./_autosetup: line 7: syntax error near unexpected token `$'in\r''
>> '/_autosetup: line 7: `case `echo "testing\c"; echo 1,2,3`,`echo -n 
>> testing; echo 1,2,3` in
>>
>> I realized that I was using the Cygwin default compiler since it was 
>> first on the PATH list, but after setting MinGW to be called first I 
>> got the following error:
>>
>> $ make -f Makefile.mingw
>> g++ -c ../api/boinc_api.cpp -o boinc_api.o  -I".." -I"../db" 
>> -I"../lib" -I"../api" -I"../zip" -I"../win_build" -D__DEBUG__ -gstabs 
>> -g3 --include ../ve
>> rsion.h -DEINSTEINATHOME_CROSS_BUILD -DMINGW_WIN32 -DWIN32 -D_WIN32 
>> -D_WIN32_WINDOWS=0x0410 -D_MT -DNDEBUG -D_WINDOWS  -DBOINC -DNODB 
>> -D_CONSOLE -mtun
>> e=pentium-m -fexceptions -march=i386 -O2
>>
>> This application has requested the Runtime to terminate it in an 
>> unusual way.
>> Please contact the application's support team for more information.
>> make: *** [boinc_api.o] Error 3
>>
>>
>> On 5/25/2010 1:26 PM, Nx Hien wrote:
>>     
>>> Are you compiling BOINC source code using Msys(MinGW command line UI) 
>>> or Cygwin?
>>> Before compiling BOINC source code, did you type ./_autosetup? 
>>> (eventhough I did not remember if it is necessary).
>>>
>>> ------------------------------------------------------------------------
>>> *From:* Shane Reilly <[email protected]>
>>> *To:* Nx Hien <[email protected]>
>>> *Sent:* Tue, May 25, 2010 12:21:52 PM
>>> *Subject:* Re: [boinc_dev] Compilation Documentation - DevC++
>>>
>>> I downloaded the latest version of the BOINC source code and the 
>>> latest version of MinGW and Cygwin on a Windows machine. It seems 
>>> that "share.h" is not available.
>>> I am having a similar problem to the one described here:
>>>
>>> http://www.mail-archive.com/[email protected]/msg00750.html
>>>
>>> Error readout:
>>>
>>> $ make -f Makefile.mingw
>>> g++ -c ../api/boinc_api.cpp -o boinc_api.o  -I".." -I"../db" 
>>> -I"../lib" -I"../api" -I"../zip" -I"../win_build" -D__DEBUG__ -gstabs 
>>> -g3 --include ../version.h -D
>>> _BUILD -DMINGW_WIN32 -DWIN32 -D_WIN32 -D_WIN32_WINDOWS=0x0410 -D_MT 
>>> -DNDEBUG -D_WINDOWS  -DBOINC -DNODB -D_CONSOLE -mtune=pentium-m 
>>> -fexceptions -march=i386 -O2
>>> In file included from ../api/boinc_api.cpp:59:
>>> ../lib/boinc_win.h:87:19: error: share.h: No such file or directory
>>> ../lib/boinc_win.h:132:21: error: dbghelp.h: No such file or directory
>>> ../lib/boinc_win.h:152:1: warning: "__TEXT" redefined
>>> In file included from 
>>> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../include/w32api/windef.h:253,
>>>                  from 
>>> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../include/w32api/windows.h:48,
>>>                  from ../lib/boinc_win.h:86,
>>>                  from ../api/boinc_api.cpp:59:
>>> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../include/w32api/winnt.h:136:1: 
>>> warning: this is the location of the previous definition
>>> In file included from ../api/boinc_api.cpp:64:
>>> ../lib/win_util.h: In function `std::wstring A2W(const std::string&)':
>>> ../lib/win_util.h:35: error: `_alloca' was not declared in this scope
>>> ../lib/win_util.h: In function `std::string W2A(const std::wstring&)':
>>> ../lib/win_util.h:43: error: `_alloca' was not declared in this scope
>>> In file included from ../api/boinc_api.cpp:88:
>>> ../lib/str_replace.h: At global scope:
>>> ../lib/str_replace.h:36: error: new declaration `const char* 
>>> strcasestr(const char*, const char*)'
>>> /usr/include/string.h:64: error: ambiguates old declaration `char* 
>>> strcasestr(const char*, const char*)'
>>> ../api/boinc_api.cpp: In member function `void GRAPHICS_APP::run(char*)':
>>> ../api/boinc_api.cpp:870: warning: deprecated conversion from string 
>>> constant to `char*'
>>> ../api/boinc_api.cpp:872: warning: deprecated conversion from string 
>>> constant to `char*'
>>> make: *** [boinc_api.o] Error 1
>>>
>>>
>>> On 5/24/2010 6:27 PM, Nx Hien wrote:
>>>       
>>>> Hi,
>>>>
>>>> You can use MinGW to build your application on Windows. 
>>>> http://www.mingw.org/wiki/HOWTO_Install_the_MinGW_GCC_Compiler_Suite
>>>>
>>>> In BOINC source code, in the lib/ folder, there is a file called 
>>>> Makefile.mingw. Go inside lib/, type "make -f Makefile.mingw". And 
>>>> it should works.
>>>>
>>>> Best,
>>>>
>>>> ------------------------------------------------------------------------
>>>> *From:* Shane Reilly <[email protected]>
>>>> *To:* [email protected]
>>>> *Sent:* Mon, May 24, 2010 4:16:24 PM
>>>> *Subject:* [boinc_dev] Compilation Documentation - DevC++
>>>>
>>>> From the documentation at these two sites:
>>>>
>>>> http://boinc.berkeley.edu/trac/wiki/CompileApp
>>>> http://boinc.berkeley.edu/trac/wiki/CompileApp?version=8&format=txt 
>>>> <http://boinc.berkeley.edu/trac/wiki/CompileApp?version=8&format=txt>
>>>>
>>>> According to the documentation at
>>>> <http://boinc.berkeley.edu/trac/wiki/CompileApp>:
>>>>
>>>> "If you can't or don't want to use Visual Studio to build applications,
>>>> the easiest alternative is Dev-C++
>>>> <http://www.bloodshed.net/devcpp.html>, an open-source development
>>>> environment based on the GCC compilers. Use the MinGW compile option."
>>>>
>>>> Unfortunately there is no documentation on how to do it. In the file at
>>>> <http://boinc.berkeley.edu/trac/wiki/CompileApp?version=8&format=txt 
>>>> <http://boinc.berkeley.edu/trac/wiki/CompileApp?version=8&format=txt>> 
>>>> it
>>>> states:
>>>>
>>>> "TODO: develop a project file for Dev-C++. It should be similar to the
>>>> Visual Studio project file (i.e. it should include what it needs from
>>>> boinc/)."
>>>>
>>>> This would be very helpful. I have no experience with DevC++.
>>>>
>>>> _______________________________________________
>>>> boinc_dev mailing list
>>>> [email protected] <mailto:[email protected]>
>>>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>>>> To unsubscribe, visit the above URL and
>>>> (near bottom of page) enter your email address.
>>>>
>>>>         
>>>       
>>     
>
> _______________________________________________
> boinc_dev mailing list
> [email protected]
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>   

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to