* Plugins Wizard: Added target variables:
WX_CFG
WX_COMPILER
WX_SUFFIX
WX_VERSION
Also, fixed build errors when using wxWidgets 3.0.
NOTE: The user still has to rename the path "devel" to "devel30".
Have you seen this patch: https://sourceforge.net/p/codeblocks/tickets/481/ ?
bluehazzard - 2017-02-27
Ok, so i reworked the script future:
1) Remove wx2.6 support
2) Add support for wx3.0 and wx3.1, make wx2.8 default
3) Changes for the windows build:
3.1) remove -ansi compiler option
3.2) add -std=gnu++11 compiler option
4) Changes for unix:
4.1) add option to choose system default wx-config parameters
4.2) add --version command line parameter for the different versions of wx
5) Add target "to_codeblocks" to make the plugin debuggable (see the discussion top)
6) Move all target common compiler/linker settings to the project
7) Use platform independent squirrel scripting to copy files
Have you seen this patch: https://sourceforge.net/p/codeblocks/tickets/481/ ?any comments on this? especially the linux problems?
bluehazzard - 2017-02-27
Ok, so i reworked the script future:1) Remove wx2.6 support
2) Add support for wx3.0 and wx3.1, make wx2.8 default
3) Changes for the windows build:
3.1) remove -ansi compiler option3.2) add -std=gnu++11 compiler option
4) Changes for unix:
4.1) add option to choose system default wx-config parameters
4.2) add --version command line parameter for the different versions of wx
5) Add target "to_codeblocks" to make the plugin debuggable (see the discussion top)
6) Move all target common compiler/linker settings to the project
7) Use platform independent squirrel scripting to copy files
@bluehazzard: I'll try to find time to test it and if it is fine I'll push it.
@stahta01: I'd rather do the same. Test the patch in the ticket and report any problems with it.
`pkg-config --cflags codeblocks`
So pkg-config works for you? I do not use it on linux so i could not test it.Code`pkg-config --cflags codeblocks`
Because it is NOT working for me.
I have NOT figured out how to debug/run the plugin; but, that could easily be user error on my part; I do NOT debug/run Code::Blocks plugins very much.As i said in the ticket here i have problems and need help. What are the symptoms you are getting?
3) If i set Project->Set program's argument->Host application to $(#cb)/devel30/codeblocks the debugger does not find the host application (the log shows a empty host application). If i replace $(#cb)/devel30/codeblocks with /absolute/path/to/codeblocks it works. Can someone on a linux system test this?
-------------- Build: to_codeblocks in test43 (compiler: gcc6)---------------
Target is up to date.
Running target post-build steps
zip -j9 test43.zip manifest.xml
updating: manifest.xml (deflated 52%)
Nothing to be done (all items are up-to-date).
-------------- Run: to_codeblocks in test43 (compiler: gcc6)---------------
Checking for existence: /home/stahta01/devel/open_source_code/version_control/codeblocks_https_metadata-git/src/devel30/share/codeblocks/plugins/libtest43.so
Executing: /home/stahta01/devel/open_source_code/version_control/codeblocks_https_metadata-git/src/devel30/codeblocks --debug-log --multiple-instance --no-splash-screen --verbose -p debug (in /home/stahta01/devel/open_source_code/no_version_control/CB_wizard_testing/test43/.)
Process terminated with status -1 (0 minute(s), 0 second(s))
-------------- Run: default in test43 (compiler: gcc6)---------------
Checking for existence: /home/stahta01/devel/open_source_code/no_version_control/CB_wizard_testing/test43/libtest43.so
Executing: /home/stahta01/devel/open_source_code/version_control/codeblocks_https_metadata-git/src/devel30/codeblocks (in /home/stahta01/devel/open_source_code/no_version_control/CB_wizard_testing/test43/.)
Process terminated with status -1 (0 minute(s), 0 second(s))
(in /home/stahta01/devel/open_source_code/no_version_control/CB_wizard_testing/test43/.)i think this is the problem. The base path should be
/home/stahta01/devel/open_source_code/version_control/codeblocks_https_metadata-git/src/devel30/codeblocksso codeblocks does not find its libraries...
Thank you for the report.
What happens if you start the debugger?
`pkg-config --cflags codeblocks`
Why do you think it is bad idea?
The C::B project can not use it, because it creates the necessary (*.pc) files, but the wizard-created plugins have to use an installed codeblocks(-devel).Why do you think it is bad idea?
1. The CB Projects does not use that method.
2. That method is broken in the Debian installed CBIs it broken in our Debian-files or in the packages from the Debian repo ?
3. The only way to get it to work is to self build Code::Blocks using configure/makeIt seems to work with my Fedora (nightly-)packages, so it must be broken in some way on Debian.
The C::B project can not use it, because it creates the necessary (*.pc) files, but the wizard-created plugins have to use an installed codeblocks(-devel).Why do you think it is bad idea?
1. The CB Projects does not use that method.
But to use it in self-compiled C::B's it might be easier and more flexible to use a global variable.2. That method is broken in the Debian installed CBIs it broken in our Debian-files or in the packages from the Debian repo ?
Using the packages from the Debian repo, I believe it does NOT work. No codeblocks.pc files is installed.It should be there according to the files-list of codeblocks-dev for testing:
I will have to use my dual Linux boot to confirm this; I am building something that will take a few hours before I can reboot.
...
/usr/lib/pkgconfig/codeblocks.pc
...
Using the packages from the Debian repo, I believe it does NOT work. No codeblocks.pc files is installed.It should be there according to the files-list of codeblocks-dev for testing:
I will have to use my dual Linux boot to confirm this; I am building something that will take a few hours before I can reboot.Quote from: https://packages.debian.org/stretch/amd64/codeblocks-dev/filelist...
/usr/lib/pkgconfig/codeblocks.pc
...
@stahta01:
If I remember correctly the new project wizard has two targets one uses the pig-config file and the other is meant to be used with a self compiled cbp based build. For the other points - if some project installs are broken then these are issues that must be reported to the respective bistro maintainers. I use the pkg-config for my personal plugins and it works fine in both centos 6 and gentoo!
2. cross platform target for wx2.8 that uses the cb variableis a cross platform project even possible?
3. cross platform target for wx3.0 that uses the cb variable
any thoughts on this?I'm not sure what problem you have in mind.
I'm not sure what problem you have in mind.I want to create a plugin for msw and unix. So i start on the msw system and create a project with the wizard. Now i have to bring this to the unix system. The current way is either to