User forums > Using Code::Blocks
Struggling with wxWidgets installation
MortenMacFly:
--- Quote from: shiraz14 on August 10, 2012, 08:43:09 pm ---Have you not read the topic of this thread (Struggling with wxWidgets installation)
--- End quote ---
Did you notice that this is a Code::Blocks, and not a wxWidgets forum?
We provide basic support for wxWidgets just for convenience only. But you should use the right forum in the first place.
Jenna:
@shiraz14:
Your post started with the invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] issue, not with the wxWidgets one.
Why did you edit your post ?
Just to tell me a liar, because I wrote your issue has nothing to do with the OP's one ?
That is offending !!
Be warned, don't ever try to do such thing or leave the forum.
And please do not say you are a professional programmer, if you are not able to compile wxWidgets with the help of our wiki, it's really not that hard.
shiraz14:
@ MortenMacFly:
Thanks for the reply.
As wxWidgets is included as a plugin for Code::Blocks (& most users of Code::Blocks would presumably employ wxWidgets for their OOP projects), I would expect some assistance (though probably not extensive as you have highlighted) to be provided within this Forum. Moreover, the problem which I have surfaced has more to do with the integration and usability of wxWidgets within the Code::Blocks IDE, rather than a pure technicality relating to wxWidgets stability as a compiled binary.
@ jens:
My initial post in this thread was on the "invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] issue". However, as this problem was resolved soon after the post was published (while a new problem emerged which was also related to wxWidgets installation & usability within Code::Blocks and thus comes under the same umbrella of this topic), I have edited my initial post to reflect this new issue, so as to avoid unnecessary allocation of resources to address an issue which has already been resolved. This has occurred before anyone (including you) responded to my previous post (& I would be aware of this since I have checked the Forum prior to making the changes in my initial post), hence any further response to my post would be to my most recent post (in the thread) which discussed the problems faced in compiling a wxWidgets project in Code::Blocks, & which would also be displayed on the Forum for future reference by users who experienced similar problems. In any instance, your statement below seems to portray that changes were made to my initial post after a response has been posted to it, which would be absolutely slanderous to me.
As for professionalism, you have displayed none of that in our correspondence thus far, while your mention about my not being able to compile wxWidgets while it's not that hard to do so (with the help of the wiki) is entirely irrelevant in this respect, since I am using the pre-compiled wxPack installer, which (according to the Wiki at http://wiki.codeblocks.org/index.php?title=WxWindowsQuickRef) should not even necessitate building. In addition, I've followed the instructions in the wiki, & ran into problems akin to the likes surfaced in my previous post [& even more issues when I attempted to build wxWidgets from the downloaded source files as according to a few wikis (please see the output below for an example of the output I get in the command prompt when building the program)] - that's why I posted this issue in the Forum.
Code output:
C:\CodeBlocks\wxWidgets2.8\build\msw>mingw32-make -f makefile.gcc BUILD=release
SHARED=1 MONOLITHIC=1 UNICODE=1
if not exist gcc_mswudll mkdir gcc_mswudll
process_begin: CreateProcess(NULL, -c "if not exist gcc_mswudll mkdir gcc_mswudl
l", ...) failed.
make (e=2): The system cannot find the file specified.
mingw32-make: [gcc_mswudll] Error 2 (ignored)
gcc -E "..\..\include\wx\msw\genrcdefs.h" > "..\..\lib\gcc_dll\mswu\wx\msw\rcdef
s.h"
process_begin: CreateProcess(NULL, -c "gcc -E \"..\..\include\wx\msw\genrcdefs.h
\" > \"..\..\lib\gcc_dll\mswu\wx\msw\rcdefs.h\"", ...) failed.
make (e=2): The system cannot find the file specified.
mingw32-make: *** [..\..\lib\gcc_dll\mswu\wx\msw\rcdefs.h] Error 2
Now, if you'll excuse me, I do not wish to waste time and resources on fruitless and unproductive exchanges with you in this Forum, since the time and energy could be better spent by being channelled into something more productive and beneficial (such as resolving this issue).
Thank you.
Jenna:
--- Quote from: shiraz14 on August 11, 2012, 05:29:46 pm ---[ ... ]
@ jens:
In any instance, your statement below seems to portray that changes were made to my initial post after a response has been posted to it, which would be absolutely slanderous to me.
[...]
--- End quote ---
Your edit was after my post, just 12 seconds, but it was after my post.
That's a fact, and you can not deny it, because everyone can clearly read this.
And editing posts in a way, that they say something totally different is not a good style in any way.
My answer was given to your invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!] issue and it stays the same.
And your issue is still unrelated to C::B, but to wxWidgets and most likely an outdated version of binutils, which sometimes leads to problemas when trying to build wxWidgets.
But this is stiull a C::B forum, not a wxWidgets one.
And if you have problems compiling wxWidgets, that are not covered by our wiki, you probably should ask in the wxWidgets forum.
You have accepted our forum rules, when registering here.
Here is an excerpt:
--- Quote from: MortenMacFly on January 24, 2009, 09:14:54 pm ---This post is here to assist you in your Code::Blocks / C++ blues, by telling you what NOT to do. This is not to frighten you, but unfortunately we have to be that strict due to continuous mis-use and dis-respect.
[...]
3. Is your problem library, framework specific? There are appropriate forums for it, not the Code::Blocks forum.
4. Search before you post. If you've used other IDEs and you're moving to Code::Blocks, try reading the Wiki (e.g. http://wiki.codeblocks.org/index.php?title=FAQ) at the homepage, and if you're confused on how to set up things, SEARCH THE FORUM. Probably the answer you're looking for is in there. Remember, Google is your friend :)
[...]
7. Only after you have checked everything out and you're sure it's a Code::Blocks configuration problem / bug and not a C++ problem, post it.
[...]
Finale note: Ignoring these rules may result in the topic being (silently) locked and/or even removed completely without any notice.
In case you wonder why we are so strict: I could say: "Search the forum" - as this has been discussed a lot. To make is short: By law we (the devs/moderators) are responsible for the content of our forum. This means we need to read all posts. If you want us to continue the development of C::B and have the time to answer some of the questions that are really related to C::B, apply the rules above. It's obviously a matter of time for us.
[...]
--- End quote ---
Please respect the rules, or leave the forum.
We (admins) are forced by law to read each and any post in this forum, so please do not waste the time, we could spend in fixing bugs or enhancing C::B.
If you have questions that are really related to C::B , feel free to ask
Thank you !!
Topic locked !!
Navigation
[0] Message Index
[*] Previous page
Go to full version