Prebuilt Wxwidgets Libs For Mac
I've used wxPython 4 (4.0.1) on macos by simply installing with 'pip3.6 install wxPython'. I've also done this on Windows before using the Python.org install of python. I tried doing 'pip3.6 install wxPython' from and msys2 mingw64 shell but it didn't install/build.
It complains with ` distutils.errors.DistutilsPlatformError: VC 6.0 is not supported by this module` It seems the msvc9compiler.py file is looking at `sys.version` to find the sub-string `MSC v.`, which isn't in `sys.version`, so VERSION is set to the default of 6. Is this an msys2/mingw issue or a python issue? How do I go about getting this to work? Once I've installed wxPython, am I also able to use C to build a C app using the same wxWidgets librariers that wxPython uses (using wx-config, etc)? Brend@BJSDELL17 MINGW64 $ pip3.6 install -U wxPython Collecting wxPython Using cached Requirement not upgraded as not directly required: six in c:/msys64/mingw64/lib/python3.6/site-packages (from wxPython) (1.11.0) Installing collected packages: wxPython Running setup.py install for wxPython. Error Complete output from command C:/msys64/mingw64/bin/python3.exe -u -c 'import setuptools, tokenize;file='C:/Users/brend/AppData/Local/Temp/pip-install-8le1c189/wxPython/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read.replace(' r n', ' n');f.close;exec(compile(code, file, 'exec'))' install -record C:/Users/brend/AppData/Local/Temp/pip-record-p71raf86/install-record.txt -single-version-externally-managed -compile: running install running build WARNING: Building this way assumes that all generated files have been generated already. If that is not the case then use build.py directly to generate the source and perform the build stage.
You can use -skip-build with the bdist. or install commands to avoid this message and the wxWidgets and Phoenix build steps in the future. 'C:/msys64/mingw64/bin/python3.exe' -u build.py build Will build using: 'C:/msys64/mingw64/bin/python3.exe' 3.6.5 (default, Apr 16 2018, 10:17:38) GCC 7.3.0 64 bit (AMD64) Python's architecture is 64bit cfg.VERSION: 4.0.1 Running command: build Running command: buildwx Command 'C:/msys64/mingw64/bin/python3.exe' -c 'import distutils.msvc9compiler as msvc; mc = msvc.MSVCCompiler; mc.initialize; print(mc.cc)' failed with exit code 1.
Traceback (most recent call last): File ', line 1, in File 'C:/msys64/mingw64/lib/python3.6 distutils msvc9compiler.py', line 297, in raise DistutilsPlatformError('VC%0.1f is not supported by this module'% VERSION) distutils.errors.DistutilsPlatformError: VC 6.0 is not supported by this module Finished command: buildwx (0.124s) Finished command: build (0.124s) Command 'C:/msys64/mingw64/bin/python3.exe' -u build.py build' failed with exit code 1. Command 'C:/msys64/mingw64/bin/python3.exe -u -c 'import setuptools, tokenize;file='C:/Users/brend/AppData/Local/Temp/pip-install-8le1c189/wxPython/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read.replace(' r n', ' n');f.close;exec(compile(code, file, 'exec'))' install -record C:/Users/brend/AppData/Local/Temp/pip-record-p71raf86/install-record.txt -single-version-externally-managed -compile' failed with error code 1 in C:/Users/brend/AppData/Local/Temp/pip-install-8le1c189/wxPython/ Thanks, Brendan.
Dietmar Schwertberger 11/5/2018, 2:39 น. Is this an msys2/mingw issue or a python issue? How do I go about getting this to work? Do you need msys2? Then you probably need to patch the detection to return the correct version and maybe submit a bug report to the msys2 people. If you don't need msys2: Usually, you need cygwin for the build process as build.py calls a bash shell script, but the build command itself can run outside. E.g.: D:/Python/Python36/python.exe build.py dox etg -nodoc sip build Regards, Dietmar Brendan Simon 14/5/2018, 4:55 น.
Prebuilt Wxwidgets Libs For Mac Download
I don't strictly need to use msys2, but I've started using it at work (in preference to cygwin as it is supposed to be more Windows friendly), so I wanted to use the same tools for a work based wx C app. Msys2 does have wxwidgets 3.0.4 (and wxPython 3 with python 2.7), but I was also wanting to use wxPython 4 with Python 3.6 (as I do on my Mac) and keep the same version of tools (that's all!!) Some options are:. msys2 with wxwidgets 3.0.4 and msys2 gcc/clang compilers (using wxglade generated C layouts). Use official Python (3.6 or whatever) + pip install wxPython (assuming I can C compile against the associated wxwidgets libs). Use msys2 gcc/clang compilers to build/install wxwidgets from source (my least preferred option). Msys2 does have a few disadvantages. One major one is it's not possible to have multiple versions of packages, so not easy to have various versions for various projects.
I'll keep experimenting nepix32 15/5/2018, 7:37 น. nepix32: May 15 07:37AM -0700 Is it even possible under Windows for a Python 3.6 to use another compiler than VC 2015? I remember that the last Python I was able to compile C extensions with mingw32 was Python 3.4. MSYS2 has the following python3 packages, and they seemed be compiled with GCC.
$ pacman -Ss python3 grep 3.6 mingw32/mingw-w64-i686-python3 3.6.5-1 installed mingw64/mingw-w64-x8664-python3 3.6.5-1 installed msys/python 3.6.2-1 installed $ /mingw32/bin/python3 Python 3.6.5 (default, Apr 16 2018, 10:30:41) GCC 7.3.0 32 bit on win32 Type 'help', 'copyright', 'credits' or 'license' for more information. $ /usr/bin/python3 Python 3.6.2 (default, Sep 7 2017, 13:16:50) GCC 6.3.0 on msys Type 'help', 'copyright', 'credits' or 'license' for more information. Anyway I came to the conclusion that using prebuilt libraries wont work unless using the exact same compiler, which means I can't use the wxPython as that uses VC (I think). The only way to use it with MSYS2/MINGW, would be to build it from sources with MSYS2/MINGW tools.
Thanks, Brendan. Robin Dunn 16/5/2018, 8:54 น. nepix32: May 15 07:37AM -0700 Is it even possible under Windows for a Python 3.6 to use another compiler than VC 2015? I remember that the last Python I was able to compile C extensions with mingw32 was Python 3.4. MSYS2 has the following python3 packages, and they seemed be compiled with GCC. $ pacman -Ss python3 grep 3.6 mingw32/mingw-w64-i686-python3 3.6.5-1 installed mingw64/mingw-w64-x8664-python3 3.6.5-1 installed msys/python 3.6.2-1 installed $ /mingw32/bin/python3 Python 3.6.5 (default, Apr 16 2018, 10:30:41) GCC 7.3.0 32 bit on win32 Type 'help', 'copyright', 'credits' or 'license' for more information. $ /usr/bin/python3 Python 3.6.2 (default, Sep 7 2017, 13:16:50) GCC 6.3.0 on msys Type 'help', 'copyright', 'credits' or 'license' for more information.
Anyway I came to the conclusion that using prebuilt libraries wont work unless using the exact same compiler, which means I can't use the wxPython as that uses VC (I think).
Prebuilt Wxwidgets Libs For Mac Free
I can see that there is still a lot of topics at wxWidgets forums related to usage of shared libs or plugins with wxWidgets apps on different platform. For Windows it’s not hard to implement such app but on Linux and OS X this may be quite tricky (especially when you are not planning to use installer for your app and create the app which will work on different machines without need to recompile it). So, specially for those, who still has problems with implementation of plugins for wxWidgets apps, I created the sample which compiles and runs on all 3 platforms, has 2 types of plugins (with and without GUI), creates the relocatable application where all plugins and other libs search for dependencies using relative paths which means that you don’t need to rebuild the app on different machines to make it work. You can find the complete source code at GitHub: The project is under development since I’m writing an article about this in parallel, so you are welcome to follow the project at GitHub and try the new versions.
— Features which I plan to add in nearest updates:. Embedding of wxWidgets libs into OS X Bundle. Embedding of wxWidgets libs into application’s distro for Linux. Document/View: Support of different file formats using plugins. Communication between plugins So, stay tuned, start watching the project at GitHub!
I’ve just published the source code of wxToolBox component and a couple of sample apps at GitHub: There is a working minimal sample and `Sample IDE` app with source code, Skin Editor does not compile with new version of wxPropertyGrid and I’m not currently interested in updating the source code. The working binary version for Windows can be downloaded from this page (also attached to this post): The source code is free for commercial and non-commercial use (component and demo apps). However if anybody still wants to buy me a beer or smth, you can make a kind of `donation` through ShareIt:.
Microsoft released their several days ago. So, for those wxWidgets developers who are interested in development of Kinect-powered applications, I created a small wxWidgets-based helper library and sample application which will allow to start using Kinect SDK. Project is hosted at Google Code. For now only basic functionality is available:. Retreiving the list of installed Kinect devices.
Retrieving the IDs of devices. Starting/Stopping of frame grabbing. Grabbing depth images If you are willing to help with implementation of new features then just let me know. I will appreciate any help in improvement of current functionality. PS: To test the application and library you need to have Kinect device for sure. JSON (JavaScript Object Notation) is a lightweight data-interchange format.
It is easy for humans to read and write. It is easy for machines to parse and generate.
It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition – December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C, C#, Java, JavaScript, Perl, Python, and many others.
These properties make JSON an ideal data-interchange language. The wxJSON library is a complete implementation of the JSON data-interchange format. All JSON specifications are implemented in this library plus some extensions in the writer and in the parser class. Today wxJSON 1.1.0 was announced. This release is compatible with both wxWidgets 2.8 and 2.9. It is also compatible with wxWidgets SVN HEAD.
N ow JSON reader and writer only process UTF-8 encoded text as a stream. Also added a new wxJSONValue’s member function to get values and fixed the bugs in wxJSONValue::IsSameAs. Taking screenshots is a very common task and it was a must for one of my current projects.
What was a surprise when I understood that my favourite toolkit can’t do that in cross-platform manner. It is that wxScreenDC does not work properly under Mac OS and you can’t use Blit message for copying screen onto wxMemoryDC. After digging the Internet I found a kind of solution which used OpenGL and created wxWidgets-based class which takes screenshots also under Mac OS. It was really hard task for me because I haven’t used neither Carbon nor Cocoa before. However everything works now and I’m happy.
Here it is:. What is AxTk?
AxTk (pronounced Ay Ex Tee Kay) is an open source, C add-on for wxWidgets that helps developers create highly accessible, talking applications for users with impaired vision. It may also be useful for other impairments that benefit from a simplified user interface. AxTk features a new menu-based system that is easy to learn and use, in addition to providing adaptation for some existing GUI controls and dialogs. The developer can choose whether to use the menu system, or to adapt an existing application UI, or use a combination of methods.
AxTk is cross-platform (tested so far on Windows XP, Linux and Mac OS X 10.5), and includes text-to-speech classes with the ability to drive SAPI 5, Apple Speech Synthesis Manager, eSpeak, and Cepstral. Other speech engines can be driven by writing additional handlers. Note that AxTk is a work in progress and the API is subject to change.