Well, several times I have tried to use wxWidgets, but I aways find the instalation very confusing and dificult, so I never really installed it. The thing is, should I even bother at trying to do it? I mean, all I wanted was some kind of tool were I could build a windowed program without hard-coding all the buttons and such, but I never found a way to do this. Maybe wxWidgets was suposed to be it, but why can't I just download something that installs it for me? It just looks easyer to hard code my window then to install that thing.
Any toughts? Thanks!
I just don't get it... this is too damn ridiculously hard. What's the point with all that?
Do you have the MinGW bin directory in your path, e.g. C:\MinGW\bin? You need to have it in your path. Then, re-run the make command from the build\msw directory. And make sure that before doing that, you revert to the original, unmodified makefile.gcc.
set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0
This is probably my problem, since I never knew how to deal with the 'path'. However, when I do:Codeset path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0
;c:\mingw\bin;c:\mingw\mingw32\bin
Thanks mdelfelde! It compiled! Ito be honest, I don't really shure what to do now (didn't checked yet), but at least I know that I'm in the right track. Thanks!Happy that this helped you :)
Well May some of you know something about Ultimate++, does it work on Code::Block
Well May some of you know something about Ultimate++, does it work on Code::BlockWe don't directly support it (there is no template or anything), but there is no reason why you should not be able to use it with Code::Blocks.
Supposing that you have correctly installed mingw in c:\mingw, the most reliable (and permanent) way to put it in your path is done with these steps :
1) Open 'My Computer" in start menu (or whatever it's called in your language...)
2) Right click in 'My Computer' window, select "Properties" from menu
3) Select "Advanced" tab, then select the button right on top of Ok button (sorry, I've got Italian windows XP and don't remember the english label....)
4) In 'System Variables" (if I remember the english name...), select path and edit it, adding this at the end :Codetry it, if it's ok, you should be able to run mingw32-make from all places.;c:\mingw\bin;c:\mingw\mingw32\bin
You shouldn't really change the path to include those bin directories because CygWin and MinGW have DLLs that clobber some programs that use GTK in windows(Gaim, Gimp, etc.).[...]
DLL search path
DLL procedures are usually declared without giving a path to the DLL file. The normal Windows search order for a DLL is the following.
1. Directory from which app loaded (executable directory)
2. Current directory (can be overridden with an API call to SetDllDirectory)
3. System directory
4. 16-bit system directory
5. Windows directory
6. Directories listed in the PATH environment variable
What is more, WinXP and later have a setting where the current directory is searched only after the System and Windows directories.
Dynamic-Link Library Search Order
Starting with Windows XP, the dynamic-link library (DLL) search order used by the system depends on the setting of the HKLM\System\CurrentControlSet\Control\Session Manager\SafeDllSearchMode value.
Windows Vista, Windows Server 2003, and Windows XP SP2: The default value is 1.
Windows XP and Windows 2000 SP4: The default value is 0.
If SafeDllSearchMode is 1, the search order is as follows:
1. The directory from which the application loaded.
2. The system directory. Use the GetSystemDirectory function to get the path of this directory.
3. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched.
4. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
5. The current directory.
6. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key.
If SafeDllSearchMode is 0, the search order is as follows:
1. The directory from which the application loaded.
2. The current directory.
3. The system directory. Use the GetSystemDirectory function to get the path of this directory.
4. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched.
5. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
6. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key.
There are still problems, trust me, I've run into them. System stability dropped significantly. ANY program that uses a DLL in it's home directory that happens to have the same name as one in the cygwin\bin or cygwin\usr\bin directories will be clobbered. This applies for mingw also. Windows searches %PATH% for DLLs, then it searches the current working directory. Read what I wrote in another thread: http://forums.codeblocks.org/index.php?topic=3550.0 (http://forums.codeblocks.org/index.php?topic=3550.0)
le meow