Recent Posts

Pages: 1 ... 5 6 7 8 9 [10]
91
Plugins development / Re: BrowseTracker dialog is not closing
« Last post by darmar on January 07, 2021, 09:00:59 pm »
I just a bit played with the code and found that uncommenting the last line in function BrowseSelector::Create enables BrowseTracker to function properly:

  -  //?m_listBox->SetFocus();
 +  m_listBox->SetFocus();

It seems that some developer had this problem and solved it earlier. Can someone try it?
92
Using Code::Blocks / Re: [RESOLVED][MacOSX 10.15] Build CB
« Last post by Suryavarman on January 07, 2021, 08:39:06 pm »
If you want to try my building process. Here my script.

1- Put the script in a new folder

2- (OPTIONAL) Open the script and uncomment the line 75 to install my dependencies choices.BUT BE AWARE CAN BE DANGEROUS FOR YOUR OWN CB building process.

3- Open a terminal

4- run the script

5- and follow the instructions.

At the end you will have the same Codeblocks.app as me.
93
Using Code::Blocks / Re: [RESOLVED][MacOSX 10.15] Build CB
« Last post by Suryavarman on January 07, 2021, 08:12:30 pm »

I use wxWidgets v3.1.4

git clone https://github.com/wxWidgets/wxWidgets.git wxwidgets-code
cd wxwidgets-code
git checkout "tags/v3.1.4"
git submodule update --init --recursive

git log

Code: [Select]
commit 6cdaedd42ba59331b3dc4ead50e0bac76ae14c19 (HEAD, tag: v3.1.4)
Author: Vadim Zeitlin <[email protected]>
Date:   Wed Jul 22 19:20:06 2020 +0200

    Fill in the binaries SHA-1 checksums

94
Using Code::Blocks / Re: [RESOLVED][MacOSX 10.15] Build CB
« Last post by oBFusCATed on January 07, 2021, 07:28:23 pm »
It will require wxCHECK_VERSION marcos I suppose. Or it is something broken in wx and they should fix it.
But it must be investigated first.

Can you post the exact commit hash of wxWidgets you're using and it needs this change?
You tried to post it before, but you post was really confusing.
95
I found a difference compared to other programs: programs are of type "application/executeable". My program was of type "application/x-sharedlib.
This was suspicious to me. The important suggestion I found here:

https://stackoverflow.com/questions/41398444/gcc-creates-mime-type-application-x-sharedlib-instead-of-application-x-applicati

I rebuild my program with linker flag -no-pie and, voila, the program is treated as "application/executeable".

Cheers,
Axel
96
Using Code::Blocks / Re: [RESOLVED][MacOSX 10.15] Build CB
« Last post by Suryavarman on January 07, 2021, 05:52:55 pm »
I have try my modification of wxscustombuttom.cpp under Mageia7 with gcc8, wx 3.0.4 and CB commit: 12281 .

wxART_ORTHER_C is not a wxString but a const char [14].
Code: [Select]
wxthings/wxscustombutton.cpp: Dans la fonction membre « virtual void wxsCustomButton::OnBuildCreatingCode() »:
wxthings/wxscustombutton.cpp:126:98: error: requête du membre « wx_str » dans « ("wxART_OTHER_C") », lequel est de type non classe « const char [14] »
             Codef(_T("%C(%W,%I,%t,%i,%P,%S,%s,%V,%N);\n"),m_Label.wx_str(),&m_Bitmap,wxART_OTHER.wx_str(),Style.wx_str());
                                                                                                  ^~~~~~
wxthings/wxscustombutton.cpp:130:86: error: requête du membre « wx_str » dans « ("wxART_OTHER_C") », lequel est de type non classe « const char [14] »
                 Codef(_T("%ASetBitmapSelected(%i);\n"),&m_BitmapSelected,wxART_OTHER.wx_str());
                                                                                      ^~~~~~
wxthings/wxscustombutton.cpp:135:82: error: requête du membre « wx_str » dans « ("wxART_OTHER_C") », lequel est de type non classe « const char [14] »
                 Codef(_T("%ASetBitmapFocus(%i);\n"),&m_BitmapFocused,wxART_OTHER.wx_str());
                                                                                  ^~~~~~
wxthings/wxscustombutton.cpp:140:86: error: requête du membre « wx_str » dans « ("wxART_OTHER_C") », lequel est de type non classe « const char [14] »
                 Codef(_T("%ASetBitmapDisabled(%i);\n"),&m_BitmapDisabled,wxART_OTHER.wx_str());
                                                                                      ^~~~~~
make[4]: *** [Makefile:902: wxthings/wxscustombutton.lo] Error 1

97
Using Code::Blocks / Re: How to get a bin-file working as standalone program with GUI?
« Last post by Panama on January 07, 2021, 05:42:34 pm »
@oBFusCATed:
Thanks meanwhile! I have a raw idea, what the shared libraries are for and how that concept works.

I feel, that my application lacks of the information, where the necessary libs are to find. So I will fiddling around the next weeks to get it work.
An appropriate tutorial or a short hint "put a path like this in the build options like that" would probably have been enough for me.

Thanks again,
Cheers, Axel
98
Using Code::Blocks / Re: [MacOSX 10.15] Build CB
« Last post by Suryavarman on January 07, 2021, 05:32:47 pm »
OO yes. That's it.

I forgot the make install (not in my script).

It's work :).
Thank you oBFusCATed for your help.

Code: [Select]
Name             : Code::Blocks
Version          : svn-r12286
SDK Version      : 2.6.0
Scintilla Version: 3.7.5
Author           : The Code::Blocks Team
E-mail           : [email protected]
Website          : http://www.codeblocks.org

wxWidgets Library (wxMac port)
Version 3.1.4 (Unicode: wchar_t, debug level: 0),
compiled at Jan  7 2021 14:31:38

Runtime version of toolkit used is 10.15.



There some minor problems:
The zoom is initiate with a very small value.
And the second one the compiler say :
Code: [Select]
warning: include location '/usr/local/include' is unsafe for cross-compilation [-Wpoison-system-directories]
99
Using Code::Blocks / Re: [MacOSX 10.15] Build CB
« Last post by oBFusCATed on January 07, 2021, 04:44:04 pm »
You have to do make; make install and then you have to run the bundle.sh script. After that you have to use the executable inside the CodeBlocks.app folder. Using the executable copied by make install won't work.
100
Panama:
LD_LIBRARY_PATH is not a global variable, whatever that means.
You can override it in the console just before you start your application.
This is what C::B does. You can see the value used by C::B in the build log or the debugger log.

It is clear that C::B works correctly, because the application starts correctly when you hit the Run/Debug buttons. :)
But the thing that it makes it kinda "just works" catches you by surprise, when you don't have C::B to help you setup things.

p.s. You're not the first one which complains about this.
p.p.s. If you'll spend lots of time developing/maintaining this application I advise you to learn how shared libraries work on linux. It will minimize the confusion even if the topic is not easy to grasp.
Pages: 1 ... 5 6 7 8 9 [10]