Recent Posts

Pages: 1 ... 5 6 7 8 9 [10]
91
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by stahta01 on February 21, 2020, 05:30:28 am »
Post the current build log?
And, are you wanting to build an wxWidgets shared/DLL or a static library?

Because, what you have posted conflicts with each other.

Edit from build/msw/config.gcc
Code: [Select]
# Type of compiled binaries [debug,release]
BUILD ?= debug

# Should debugging info be included in the executables? The default value
# "default" means that debug info will be included if BUILD=debug
# and not included if BUILD=release. [0,1,default]
DEBUG_INFO ?= default

# Value of wxDEBUG_LEVEL. The default value is the same as 1 and means that all
# but expensive assert checks are enabled, use 0 to completely remove debugging
# code. [0,1,default]
DEBUG_FLAG ?= 1

Edit2: To have the most debug information I think you need to use "DEBUG_FLAG=2" when building wxWidgets.

Edit3: See wx/debug.h for more information

Tim S.
92
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by spflanze on February 21, 2020, 04:50:35 am »
Thanks for your reply. I made all those global file fields blanks as you recommended. That path is now a valid one. I made a bad assumption when I thought the content of those fields would be appended to the base. I see now they are not, and are a complete replacement for what is default.

The project still does not compile. In the error message I see: -Winvalid-pch. I think this is a message from the make file that says something has gone wrong with precompiled headers. Your suggestions about troubleshooting this would be appreciated.

This is the command I used to compile wxWidgets.
Code: [Select]
mingw32-make -f makefile.gcc SHARED=1 UNICODE=1 BUILD=releaseIt is copied from this web page: https://wiki.wxwidgets.org/Compiling_wxWidgets_with_MinGW
If I were to compile for those higher levels of debug ability, how would this be changed?
93
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by stahta01 on February 21, 2020, 02:57:49 am »
Quote
For use in debug mode is a separate debug compilation of wxWidgets 3.1.3 required?

No, but sometimes you might wish to make one with all the symbols.
The wxWidgets in 3.1 is normally build with debug symbols; but, it can be built with more or less debug information. wxWidgets 2.8 was normally built without debug information. Not sure about 3.0

Tim S.
94
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by stahta01 on February 21, 2020, 02:51:48 am »
FYI:

Quote
bin: \bin
Is wrong, you will likely want it to be default of blank which results in a bin folder under the base path or
bin: C:\wxWidgets-3.1.3\lib
That would point you to the DLLs or static libraries

Tim S.


95
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by stahta01 on February 21, 2020, 02:45:31 am »
Quote
base: C:\wxWidgets-3.1.3
lib: \lib\gcc_lib

I would go with the normal default for windows of empty string which results in C:\wxWidgets-3.1.3\lib
Or you could use
lib: C:\wxWidgets-3.1.3\lib\gcc_lib

Then
"$(#wx.lib)\gcc_dll\mswu"
would need to be
"$(#wx.lib)\gcc_lib\mswu" if using the normal default
or
"$(#wx.lib)\mswu" if using my next suggestion

Tim S.


96
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by spflanze on February 21, 2020, 02:00:47 am »
That is where 3.1.2 was. I missed that earlier. Thanks. Now I am seeking to use the wx variable to make future upgrades easier. In the path: "Settings => Global variables => wx" I have these settings:
Code: [Select]
base: C:\wxWidgets-3.1.3
include:
lib: \lib\gcc_lib
bin: \bin

For my project, for which I will name here "Designer", I right click Designer in the Projects tab of the Management pane, and navigate the path: Designer => Build Options => Debug => Search Directories (tab) -> Compiler (tab) I have:
Code: [Select]
$(#wx.lib)\gcc_dll\mswuWhen I attempt to compile my project in Code::Blocks I get the error:
Code: [Select]
[ 14.3%] mingw32-g++.exe -Wall -pipe -mthreads -Winvalid-pch -include wx_pch.h -D__GNUWIN32__ -D__WXMSW__ -DwxUSE_UNICODE -DWX_PRECOMP -g -D__WXDEBUG__ -Winline -Wall -pg -m64 -g -g3 -I..\Libraries\cminpack-1.3.6 -I\lib\gcc_lib\gcc_dll\mswu -c "C:\Software\Designer\wx_pch.h" -o "wx_pch.h.gch\Debug_TIA Designer_wx_pch_h_gch"

Execution of 'mingw32-g++.exe -Wall -pipe -mthreads -Winvalid-pch -include wx_pch.h -D__GNUWIN32__ -D__WXMSW__ -DwxUSE_UNICODE -DWX_PRECOMP -g -D__WXDEBUG__ -Winline -Wall -pg -m64 -g -g3 -I..\Libraries\cminpack-1.3.6 -I\lib\gcc_lib\gcc_dll\mswu -c "C:\Software\Designer\wx_pch.h" -o "wx_pch.h.gch\Debug_TIA Designer_wx_pch_h_gch"' in 'C:\Software\Designer' failed.
In this compile command I see the path: -I\lib\gcc_lib\gcc_dll\mswu
My expectation was that the text "$(#wx.lib)" would be replaced by "C:\wxWidgets-3.1.3\lib\gcc_lib . This has not happened. The base "C:\wxWidgets-3.1.3\" is missing. Have I misunderstood how this global variable works?

For use in debug mode is a separate debug compilation of wxWidgets 3.1.3 required?


97
Help / Re: Code::Blocks build dependencies under ubuntu?
« Last post by oBFusCATed on February 20, 2020, 11:45:24 pm »
Using packages means that you can uninstall all added files. This is the job of the package system - to manage all the files of the package.

make install/uninstall doesn't track files, they use the build rules to do this job, so if the rules change between the install and uninstall steps the uninstall won't be complete and there would be misery and suffering.
98
Help / Re: Code::Blocks build dependencies under ubuntu?
« Last post by cacb on February 20, 2020, 09:18:35 pm »
But why would you care where a package is installed? Its default is just fine. The idea is that locally build package is superseding the distro version, so you have no conflicts. Debian/ubuntu are shipping old versions anyway.

In this case the default is fine, I agree. My comment was actually inspired by what you said in another thread about installing to places where you can just delete without causing conflicts with other software.
http://forums.codeblocks.org/index.php/topic,22137.msg150685.html#msg150685
99
Help / Re: Code::Blocks build dependencies under ubuntu?
« Last post by oBFusCATed on February 20, 2020, 08:53:07 pm »
No idea, I don't use debian regularly, I just make sure it builds on ubuntu, because of popularity.
But why would you care where a package is installed? Its default is just fine. The idea is that locally build package is superseding the distro version, so you have no conflicts. Debian/ubuntu are shipping old versions anyway.
100
Help / Re: Code::Blocks build dependencies under ubuntu?
« Last post by cacb on February 20, 2020, 08:44:22 pm »
Yes, in the configure script.
Ok, I guess that refers to the configure.ac file. I am not familiar with that syntax, but it is probably the correct answer  :P

If you want to have problem free building just use
Code: [Select]
dpkg-buildpackage -us -uc
Thanks, you are right, this works fine. I checked the meaning of the options -us -uc and I guess it just means avoiding some warnings of "unsigned source".

Using dpkg-buildpackage you get *.deb files that install to /usr, which is fine for this kind of virtual machine that I am setting up. But if you want it in a different location I guess the correct way is to edit debian/rules and under DEB_CONFIGURE_EXTRA_FLAGS set the --prefix=/usr to something different.

Pages: 1 ... 5 6 7 8 9 [10]