Do you have a question about makefiles, a compiler or IDE you are using and need to know how to set it up for wxWidgets or why it doesn't compile but other IDE's do ? Post your questions here.
/Volumes/Home/pvn/git/wx/wxwidgets-3.1.5/samples/menu/menu.cpp:191:5: error: unknown type name 'wxFileHistory'
wxFileHistory* m_fileHistory;
^
/Volumes/Home/pvn/git/wx/wxwidgets-3.1.5/samples/menu/menu.cpp:454:5: error: cannot initialize object parameter of type 'wxFrame' with an expression of type 'MyFrame'
frame->Show(true);
^~~~~
/Volumes/Home/pvn/git/wx/wxwidgets-3.1.5/samples/menu/menu.cpp:457:5: error: cannot initialize object parameter of type 'wxFrameBase' with an expression of type 'MyFrame'
frame->SetStatusText("Welcome to wxWidgets menu sample");
^~~~~
/Volumes/Home/pvn/git/wx/wxwidgets-3.1.5/samples/menu/menu.cpp:471:5: error: cannot initialize object parameter of type 'wxTopLevelWindowBase' with an expression of type 'MyFrame'
SetIcon(wxICON(sample));
^~~~~~~
/Volumes/Home/pvn/git/wx/wxwidgets-3.1.5/samples/menu/menu.cpp:481:5: error: cannot initialize object parameter of type 'wxFrameBase' with an expression of type 'MyFrame'
CreateStatusBar();
^~~~~~~~~~~~~~~
1. Unpack wxWidgets 3.1.5 in ~/
2. Run the Terminal
3. In the Terminal do:
3a cd ~/wxWidgets-3.1.5
3b. mkdir buildMac
3c. cd buildMac
3d. ../configure --enable-debug --with-cocoa && make
33. cd samples && make
If you will get an error at ANY point - please come back and post an error.
Hi,
It is de-facto a standard to make a build dynamic on *nix/Mac.
If you really, really, really need a static build, change step 3d to read:
3d. ../configure --enable-debug --with-cocoa --disable-shared && make
but be prepared to have a legal consequences from Apple or any company whose software will be used by your program for License violation.
Or even worse - have a random crashes because the 3rd party library used by you program is ABI-incompatible with the Apple ones. And good luck trucking it down.
Thank you.
BTW.: I don't use "CMake-thingy". The only thing its useful for is when you distribute your application to the end user as part of the bigger software that already is using "CMake-thingy".
Otherwise wxWidgets provides everything you need to build the library and the samples.
It is like when you going to cry "Eurika", but then this law was already in place for the past 2000 years, if not more.
I don't know why the ./configure build is fine with this, but the CMake build fails , so it seems that you should make this change in your 3.1.5 code
(btw, this has nothing to do with a static or dynamic build)
Hi,
My point is that configure build is OK - whether its a dynamic or static linkage.
And this is the way wxWidgvets is building for the past 20+ years.
You can try to argue you point in wx-users ML (sign-up is required): here.
Thank you.
BTW, the automatic wxWidgets build/test framework doesn't fail and didn't fail even when configuring with CMake-thingy.
Hi,
I am not - automatic builds on Travis does.
And obviously there was no breakage at the time of release.
You need to understand - wxWidgets provide everything you need to start developing (Makefile to build the library and samples and the samle code to start your work off of).
There is no need to regenerate the Makefile's - its already been done for you.
CMake is not a build tool - its a configuration tool designed to create Makefile for the build. But since its already been done - all you need to do is run configure and make.
wxWIdgets team until very recently didn't care about CMake-thingy. They didn't provide support for it. Because it is NOT NEEDED.
Moreover - this forum is for users of the library. Nobody here is affiliated with it in any way. No core wxWidgets developers come here to help you. I'm ust like you - a user of the library. All I'm doing is running configure and make and it gives me wxWIdgets library. There is no need to run CMake-thingy. In fact I'm scared to run it to build wxWidgets itself and any and all samples,, because everything is already generated and I can build it by simply doing:
cd <build_dir>/samples/minimal && make
No need to run anything extra (reinvent the wheel/recreate the bike).
I suggest for you to stick with configure to build the library and samples and for everything else use whatever your heart desires.
And, I would remove "-DwxBUILD_COMPATIBILITY=3.1" because it makes no sense to me as an option to try at first; maybe after you get it to work without it.
But, I am not really an cmake user; but, I do use configure/make to build wxWidgets a lot.