While trying to build a Codeblocks version from source, the gcc compiler asks for a nonexistent file (-lwxmsw33u) and then fails. The wxwidgets-3.3.2 library (wx33) was built using the c++23 standard. The section of the buid log in included.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@FDMuir ,
Did you try C::B forum?
How exactly did you build the library?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Firstly, as has been said, this is not a wxWidgets Issue. Please do not use wxWidgets Issues for help with 3rd party software issues: In this case, use Code::Blocks support channels to help you buildCode::Blocks.
Secondly, did you check whether you actually have file libwxmsw33u.a in your C:\wxWidgets-3.3.2\lib\gcc_dll folder?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@FDMuir ,
First of all - any reason you needed to modify config.gcc file?
Everything you did could be supplied by the command line.
Second - did you check the “OUT10” file to see if the compilation was ?
And finally as PB suggested- did you check if the file exist?
Thank you.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@oneeyeman1 @PBfordev
Thanks for your comments. I'll deal with 3rd party staff in the future!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
In the other issue you had opened you were already told that if you use non-empty CFG, the output directory is different from what C::B expects it to be, but it looks like you've just totally ignored this...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Sorry, I don't understand what do you mean (I just hope you don't seriously believe you need gcc or ld to be changed...), but please internalize the simple fact: if you set CFG, then the output files are created in the directory with the value of CFG in its name and you can't expect them to be found in the directory without CFG in its name.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
The simple fact has been internalized.
It really doesn't look so.
I don't need to have gcc or ld changed. I just want to ask Brecht Sanders if any changes had been made to ld that would cause it to not be able to find a particular file.
It is not looking for it in the directory where the file exists. As stated above. Many times.
I won't try to prevent you from making fool of yourself by asking anybody about it, but let me assure you that there have been no changes to gcc or ld that have anything to do with this issue.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
I don't know how to explain it any better. You clearly didn't read the original reply, you didn't understand when I wrote the comment above referencing and you didn't understand my comment restating above in spite of replying to it saying that you understood.
I give up.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()