User forums > Using Code::Blocks

missing wx/setup.h

<< < (5/5)

PB:

--- Quote from: bdad on December 14, 2022, 11:21:36 pm ---mysys2.exe is in R:\mysys64.  I was pretty sure I set the path, but just done it again, with same result.

--- Quote ---R:\wxWidgets-3.2.1\build\msw>set path=r:\mysys64\mingw64\bin%path%

--- End quote ---

--- End quote ---
Are you sure your default PATH starts with a semicolon? If not, then the command above does NOT set the correct path to GCC (i.e., you are missing a semicolon between "bin" and "%path%").

Why not just use tested working commands available, modified for your path? In other words, do not retype the commands you think are correct, copy and paste them, adjust the path, check they are correct and then run them.

There is no reason to use full path to the make executable or the makefile itself.

Lastly, read the error messages and try to understand them. By doing this, you will have a chance to figure the problem by yourself.

For example, in one of your previous posts, the system told you "'mingw32-make' is not recognized as an internal or external command" yet you assumed there is an issue with a makefile. In your last post, it is clear that the issue not just with GCC but also with make since you had to use a full path; this means that you did not set PATH correctly.

BTW, all issues so far have nothing to do with wxWidgets, Code::Blocks, or my guide; it's just the most basic C++ / Windows knowledge.

bdad:
Well spotted wrt the semi-colon. I think I mentioned earlier that it may be a typo. I did not want to mess with your batch files. Anyway, I have now run your build -library-shared.bat, however i was disappointed that after possibly an hour of build, it merely finished. I would have expected a rendition of the National Anthem, and setting off of fireworks! (Misleadingly, that window closed, leaving my previous one with the error messages showing...)
All the files appear to be present in gcc-dll folder, I will run your minimal sample test.
I want to install the static build version, if that can coexist with the debug/release versions. Do I just delete the two folders you mention  in cleaning the gcc builds, and run the static build batch file?

PB:

--- Quote from: bdad on December 15, 2022, 12:19:07 pm ---Anyway, I have now run your build -library-shared.bat, however i was disappointed that after possibly an hour of build, it merely finished.

--- End quote ---
Had you followed the advice I gave in the guide and even repeated here (i.e., use the parallel build), it should have taken much less time.


--- Quote from: bdad on December 15, 2022, 12:19:07 pm ---Misleadingly, that window closed, leaving my previous one with the error messages showing...)

--- End quote ---
I do not see what is misleading about the window with successful build closing, as described in the guide and the batch file, the window is left open only when the build fails, so the build error messages remain available.


--- Quote from: bdad on December 15, 2022, 12:19:07 pm ---I want to install the static build version, if that can coexist with the debug/release versions. Do I just delete the two folders you mention  in cleaning the gcc builds, and run the static build batch file?

--- End quote ---
You are mixing two things here, static/shared (affected by the value of the build parameter "SHARED") and debug/release (affected by the value of the build parameter "BUILD"). They are used together, you cannot have one without other, e.g. you can have a static debug build, a shared release build, and/or any other of the four possible combinations. They do not affect each other. As described in the guide, the libraries for the debug build have an extra "d" in their name so they can coexist in the same folder with the release libraries. Also as described there, static builds are by default generated in "WXDIR/lib/gcc_lib" while the shared ones in "WXDIR/lib/gcc_dll".

You said that my guide is overly detailed for you, but as you can see, in the end you still need to know about all these supposed "details". Had you read the guide, you wouldn't have to ask and could have saved time and effort.

Anyway, I will not nag at you anymore, it seems that that I am either unable to properly explain even the most basic things or the communication between the two of us is somehow utterly broken.

Considering that doing the things described in my guide is actually the easy part and the difficult one comes with the programming itself, I can only wish you good luck.

bdad:
I don't see our communication as being broken. I ask a question, you point me in the right direction. When, earlier, I said that your guide was too complicated for me,( or whatever), that is not a reflection on your guide, but the fact that I had hoped that the whole installation to be simpler., my not knowing what was involved in getting wxWidgets to link statically.

Anyway, thanks for your help, the minimal build example works fine on my system.

Navigation

[0] Message Index

[*] Previous page