Hi,
I am trying to compile some sourceforge windows projects under winelib and need some guidance regarding how to fix these errors.
bb4win =========================================== g++ -c -I. -I/usr/local/wine/include -g -O2 -fpermissive -fno-for-scope -D_REENTRANT -o BB Api.o BBApi.cpp In file included from BBApi.cpp:34: Menu/MenuMaker.h:53:16: io.h: Ingen sådan fil eller filkatalog BBApi.cpp: In function `const CHAR* GetBBVersion()': BBApi.cpp:80: warning: passing NULL used for non-pointer argument passing 2 of `BOOL GetFileVersionInfoA(const CHAR*, long unsigned int, long unsigned int, void*)' BBApi.cpp:80: warning: argument to non-pointer type `long unsigned int' from NULL BBApi.cpp: In function `CHAR* ReadValue(const CHAR*, const CHAR*, long int*)': BBApi.cpp:458: `stricmp' undeclared (first use this function) BBApi.cpp:458: (Each undeclared identifier is reported only once for each function it appears in.) BBApi.cpp: In function `void Log(const CHAR*, const CHAR*)': BBApi.cpp:611: `_strtime' undeclared (first use this function) BBApi.cpp: In function `COLORREF ParseLiteralColor(const CHAR*)': BBApi.cpp:891: `strnicmp' undeclared (first use this function) BBApi.cpp: In function `HINSTANCE__* BBExecute(HWND__*, const CHAR*, const CHAR*, const CHAR*, const CHAR*, int, bool)': BBApi.cpp:1409: `SHELLEXECUTEINFO' undeclared (first use this function) BBApi.cpp:1409: parse error before `;' token BBApi.cpp:1419: `si' undeclared (first use this function) BBApi.cpp:1429: `SEE_MASK_DOENVSUBST' undeclared (first use this function) BBApi.cpp:1429: `SEE_MASK_FLAG_NO_UI' undeclared (first use this function) BBApi.cpp:1430: `ShellExecuteEx' undeclared (first use this function) BBApi.cpp: In function `bool IsInString(const CHAR*, const CHAR*)': BBApi.cpp:1573: `strlwr' undeclared (first use this function) make[1]: *** [BBApi.o] Error 1 make[1]: Leaving directory `/user/home/hcs/Wine/winelib/compile/bb4win/blackbox' make: *** [blackbox] Error 2 ===========================================
NSIS/Source =========================================== gcc -c -I. -I/usr/local/wine/include -g -O2 -fPIC -D_REENTRANT -o Ui.o Ui.c Ui.c: In function `set_language': Ui.c:275: warning: comparison is always false due to limited range of data type gcc -c -I. -I/usr/local/wine/include -g -O2 -fPIC -D_REENTRANT -o bgbg.o bgbg.c gcc -c -I. -I/usr/local/wine/include -g -O2 -fPIC -D_REENTRANT -o bin2h.o bin2h.c gcc -c -I. -I/usr/local/wine/include -g -O2 -fPIC -D_REENTRANT -o exec.o exec.c exec.c: In function `ExecuteEntry': exec.c:1006: `IShellLink' undeclared (first use in this function) exec.c:1006: (Each undeclared identifier is reported only once exec.c:1006: for each function it appears in.) exec.c:1006: `psl' undeclared (first use in this function) exec.c:1014: `CLSID_ShellLink' undeclared (first use in this function) exec.c:1015: `IID_IShellLink' undeclared (first use in this function) make[1]: *** [exec.o] Error 1 make[1]: Leaving directory `/user/home/hcs/Wine/winelib/compile/NSIS/Source/exehead' make: *** [exehead] Error 2 ===========================================
wnsr/wnsrtool =========================================== g++ -c -I. -I/usr/local/wine/include -g -O2 -fpermissive -fno-for-scope -D_REENTRANT -o logfileCode.o logfileCode.cpp logfileCode.cpp: In function `void writelogline(FILE*, char, char*, char*, int, long unsigned int)': logfileCode.cpp:40: `_strtime' undeclared (first use this function) logfileCode.cpp:40: (Each undeclared identifier is reported only once for each function it appears in.) logfileCode.cpp:41: `_strdate' undeclared (first use this function) make: *** [logfileCode.o] Error 1 ===========================================
On Wed, 29 Jan 2003, Hans Christian Studt wrote:
Hi,
I am trying to compile some sourceforge windows projects under winelib and need some guidance regarding how to fix these errors.
bb4win
g++ -c -I. -I/usr/local/wine/include -g -O2 -fpermissive -fno-for-scope -D_REENTRANT -o BB Api.o BBApi.cpp
Please use wineg++ instead of g++, and winegcc instead of gcc. Do the apps you are trying to compile build under MinGW? If so, all you have to do to the makefiles (in theory) is this:
-CC=gcc -CXX=g++ -RC=windres +CC=winegcc +CXX=wineg++ +RC=wrc
If it does not work like this, please report back on the list.
On the other hand if they don't build under MinGW currently, your best bet is to get them to build & run under MinGW first, and try to port them to winelib after that.
Dimitrie O. Paun wrote:
On Wed, 29 Jan 2003, Hans Christian Studt wrote:
Hi,
I am trying to compile some sourceforge windows projects under winelib and need some guidance regarding how to fix these errors.
bb4win
g++ -c -I. -I/usr/local/wine/include -g -O2 -fpermissive -fno-for-scope -D_REENTRANT -o BB Api.o BBApi.cpp
Please use wineg++ instead of g++, and winegcc instead of gcc. Do the apps you are trying to compile build under MinGW? If so, all you have to do to the makefiles (in theory) is this:
-CC=gcc -CXX=g++ -RC=windres +CC=winegcc +CXX=wineg++ +RC=wrc
If it does not work like this, please report back on the list.
On the other hand if they don't build under MinGW currently, your best bet is to get them to build & run under MinGW first, and try to port them to winelib after that.
I you are busy I will try to look at it :-)
If you are, let me know, I'll give you a braindump of what I think needs to happen.
I just build from the CVS and I now have /usr/local/wine/tools/winegcc but I canot find wineg++
Should there be a symbolic link to winegcc or what ???
On Fri, 31 Jan 2003, Hans Christian Studt wrote:
I just build from the CVS and I now have /usr/local/wine/tools/winegcc but I canot find wineg++
Should there be a symbolic link to winegcc or what ???
Yes, it's just a symbolic link:
[dimi@dimi dimi]$ ls -l /usr/local/bin/wine* -rwxr-xr-x 1 root root 242956 Jan 15 21:09 /usr/local/bin/wine -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/wineboot -rwxr-xr-x 1 root root 396533 Jan 30 13:08 /usr/local/bin/winebuild -rwxr-xr-x 1 root root 66714 Jan 15 21:09 /usr/local/bin/wineclipsrv -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/wineconsole -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winedbg -rwxr-xr-x 1 root root 287808 Jan 30 13:08 /usr/local/bin/winedump -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winefile lrwxrwxrwx 1 root root 7 Jan 30 13:08 /usr/local/bin/wineg++ -> winegcc -rwxr-xr-x 1 root root 51173 Jan 30 13:08 /usr/local/bin/winegcc -rwxr-xr-x 1 root root 19864 Jan 15 21:09 /usr/local/bin/winelauncher -rwxr-xr-x 1 root root 97085 Jan 30 13:08 /usr/local/bin/winemaker -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winemine -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winepath -rwxr-xr-x 1 root root 1372162 Jan 15 21:09 /usr/local/bin/wineserver -rwxr-xr-x 1 root root 5726 Jan 15 21:09 /usr/local/bin/wineshelllink -rwxr-xr-x 1 root root 62872 Jan 30 13:08 /usr/local/bin/winewrap [dimi@dimi dimi]$
Dimitrie O. Paun wrote:
On Fri, 31 Jan 2003, Hans Christian Studt wrote:
I just build from the CVS and I now have /usr/local/wine/tools/winegcc but I canot find wineg++
Should there be a symbolic link to winegcc or what ???
Yes, it's just a symbolic link:
[dimi@dimi dimi]$ ls -l /usr/local/bin/wine* -rwxr-xr-x 1 root root 242956 Jan 15 21:09 /usr/local/bin/wine -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/wineboot -rwxr-xr-x 1 root root 396533 Jan 30 13:08 /usr/local/bin/winebuild -rwxr-xr-x 1 root root 66714 Jan 15 21:09 /usr/local/bin/wineclipsrv -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/wineconsole -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winedbg -rwxr-xr-x 1 root root 287808 Jan 30 13:08 /usr/local/bin/winedump -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winefile lrwxrwxrwx 1 root root 7 Jan 30 13:08 /usr/local/bin/wineg++ -> winegcc -rwxr-xr-x 1 root root 51173 Jan 30 13:08 /usr/local/bin/winegcc -rwxr-xr-x 1 root root 19864 Jan 15 21:09 /usr/local/bin/winelauncher -rwxr-xr-x 1 root root 97085 Jan 30 13:08 /usr/local/bin/winemaker -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winemine -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winepath -rwxr-xr-x 1 root root 1372162 Jan 15 21:09 /usr/local/bin/wineserver -rwxr-xr-x 1 root root 5726 Jan 15 21:09 /usr/local/bin/wineshelllink -rwxr-xr-x 1 root root 62872 Jan 30 13:08 /usr/local/bin/winewrap [dimi@dimi dimi]$
Thanks
Be sure someone fix that in the CVS.
On Fri, 31 Jan 2003, Hans Christian Studt wrote:
Be sure someone fix that in the CVS.
There's nothing to fix in CVS. make install creates that link. Did you run make install?
Hans Christian Studt wrote:
Dimitrie O. Paun wrote:
Yes, it's just a symbolic link:
Be sure someone fix that in the CVS.
No fix needed - It is correct in /usr/local/bin - sorry
Hans Christian Studt wrote:
Hans Christian Studt wrote:
Dimitrie O. Paun wrote:
Yes, it's just a symbolic link:
Be sure someone fix that in the CVS.
No fix needed - It is correct in /usr/local/bin - sorry
I the current winemaker perl script the variable is used WINE_TOOL_PATH="$WINE_ROOT:$WINE_ROOT/bin:$WINE_ROOT/tools/wrc:$WINE_ROOT/tools/winebuild" which support running of the source-three where tools/wrc exists as well as off the /usr/local/bin-three as long as gcc is used.
Now when we want to use the winegcc and wineg++ the source-three will not work. In order to make it work we need to add $WINE_ROOT/tools to WINE_TOOL_PATH and to create a symbolic link between winegcc and wineg++ in the source-three.
The question is should we support source-three or should we get rid of :$WINE_ROOT/tools/wrc:$WINE_ROOT/tools/winebuild from WINE_TOOL_PATH
On Fri, 31 Jan 2003, Hans Christian Studt wrote:
The question is should we support source-three or should we get rid of :$WINE_ROOT/tools/wrc:$WINE_ROOT/tools/winebuild from WINE_TOOL_PATH
Getting winegcc and winewrap work off of the source tree is not supported at the moment, as I said in an earlier email. It will take a lot more than pointing an environment variable, and it will not happen any time soon. Only after it stabilizes a bit should we consider modifying it to work from the tree.
So for now, if you want to play with Winelib, you have to make install it, and use it like it's meant to be used.
Dimitrie O. Paun wrote:
On Fri, 31 Jan 2003, Hans Christian Studt wrote:
The question is should we support source-three or should we get rid of :$WINE_ROOT/tools/wrc:$WINE_ROOT/tools/winebuild from WINE_TOOL_PATH
Getting winegcc and winewrap work off of the source tree is not supported at the moment, as I said in an earlier email. It will take a lot more than pointing an environment variable, and it will not happen any time soon. Only after it stabilizes a bit should we consider modifying it to work from the tree.
So for now, if you want to play with Winelib, you have to make install it, and use it like it's meant to be used.
Fine
-
Dimitrie O. Paun -
Hans Christian Studt