Thanks for accepting the pull request for the file.cpp fix. Have gone a bit further, without brew. First I cloned the googletest repo and then inside the googletest/googletest folder: $ cmake. Configuring done - Generating done - Build files have been written to: /Users/neuralshock/Repos/googletest/googletest $ make 50% Built target gtest 100% Built target gtestmain and this gives me the libgtest.a and libgtestmain.a files that are required. Some env vars have to be declared for cmake to continue past the googletest requirements: $ export grep -i gtest declare -x GTESTINCLUDEDIR='/Users/neuralshock/Repos/googletest/googletest/include/' declare -x GTESTINCLUDEDIRS='/Users/neuralshock/Repos/googletest/googletest/include/' declare -x GTESTLIBRARY='/Users/neuralshock/Repos/googletest/googletest/libgtest.a' declare -x GTESTMAINLIBRARY='/Users/neuralshock/Repos/googletest/googletest/libgtestmain.a' declare -x GTESTROOT='/Users/neuralshock/Repos/googletest/googletest/' Now I find problems with wx:) $ cmake.
![]()
CMake Error at /usr/local/Cellar/cmake/3.4.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:148 (message): Could NOT find wxWidgets (missing: wxWidgetsLIBRARIES wxWidgetsINCLUDEDIRS) Call Stack (most recent call first): /usr/local/Cellar/cmake/3.4.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:388 (FPHSAFAILUREMESSAGE) /usr/local/Cellar/cmake/3.4.3/share/cmake/Modules/FindwxWidgets.cmake:899 (findpackagehandlestandardargs) CMakeLists.txt:29 (findpackage) - Configuring incomplete, errors occurred! See also '/Users/neuralshock/Repos/pwsafe/build/CMakeFiles/CMakeOutput.log'. CMake Error at /usr/local/Cellar/cmake/3.4.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:148 (message): Could NOT find wxWidgets (missing: wxWidgetsLIBRARIES wxWidgetsINCLUDEDIRS) Call Stack (most recent call first): /usr/local/Cellar/cmake/3.4.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:388 (FPHSAFAILUREMESSAGE) /usr/local/Cellar/cmake/3.4.3/share/cmake/Modules/FindwxWidgets.cmake:899 (findpackagehandlestandardargs) CMakeLists.txt:29 (findpackage) - Configuring incomplete, errors occurred! See also '/Users/neuralshock/Repos/pwsafe/build/CMakeFiles/CMakeOutput.log'.
Added path to cmd line, it worked! Had to install Xerces as well, now hitting other issues because of version.h as mentioned above. So, my fault in the previous error - I hacked about.cpp and completely forgot it. I'm not sure what I did some time ago with wxWindows, but it's not working anymore even with 's suggestion. I can't find some of my notes. Sorry for that.
So I installed wxmac via homebrew, and CMake finds wx-config properly. Cmake output: $ cmake. Thanks for the quick reply, thats what I did (with a fresh clone).
( 163.3 KB) - added by andrius.laikina@. Libsdlmixer removed as dependency, debug enabled ( 56.9 KB) - added by software@. Debug report of installing wxWidgets ( 2.7 KB) - added by software@. For mac danzig ufc 124 fight with joe stevenson is win or going. Working portfile for wxWidgets 2.9.0 ( 1.9 KB) - added by software@. Patch for bug about no matching wxWidgetImpl::FindFromWXWidget function. Required for wxWidgets 2.9.0 Portfile ( 2.3 KB) - added by Veence (Vincent). Portfile for 'py26-wxpython-devel' ( 1.1 KB) - added by Veence (Vincent).
Patch for 'py26-wxpython-devel' ( 345 bytes) - added by Veence (Vincent). ( 695 bytes) - added by Veence (Vincent). Final patch for py26-wxwidgets-devel ( 5.2 KB) - added by jmroot (Joshua Root).
Use X11 instead of wxMac when building 64-bit Download all attachments as. Now that libsdl and libsdlmixer compile fine on 64-bit Snow Leopard, I bumped into this bug as well. It seem to be a bug in wxWidgets itself. Here is the error:./src/common/intl.cpp:2060: error: 'smScriptLang' was not declared in this scope./src/common/intl.cpp:2060: error: 'GetScriptVariable' was not declared in this scope./src/common/intl.cpp:2061: warning: 'GetScriptManagerVariable' is deprecated (declared at /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Script.h:993) And there seems to be a fix at the wxWidgets website (I have not tested it yet). I did manage to compile wxWidgets today. There are three, possibly four, 'bugs' to solve before it compiles.
Wxwidgets 2 For Mac Download![]()
I'll list them here and include my Portfile and patch script. However, I had a busy day and did not have time to test it yet.
If someone has that time, please do! Also, the settings probably only work for OS 10.5 and higher. If this portfile is to be used on other platforms as well, it will be necessary to make a variant for this specific Darwin version.
I have not done that yet. I encountered the following bugs: Bug number 1:./src/osx/carbon/utils.cpp: In function 'void wxGetMousePosition(int., int.)':./src/osx/carbon/utils.cpp:161: error: 'GetGlobalMouse' was not declared in this scope Problem: The osxcarbon GUI toolkit is selected. This ought to be the osxcocoa GUI toolkit. Or./include/wx/cocoa/cursor.h:42: error: default argument for parameter of type 'wxBitmapType' has type 'int' Problem: The cocoa GUI toolkit is selected. This ought to be the osxcocoa GUI toolkit.
Some Carbon libraries are no longer available in 64-bit. You should use Cocoa instead. Solution: change./configure -with-mac./configure -with-osxcarbon./configure -with-carbon or./configure -with-cocoa to:./configure -with-osxcocoa Bug number 2: wxWidgets/src/osx/core/printmac.cpp: In member function ‘virtual bool wxOSXPrintData::TransferFrom(const wxPrintData&)’: wxWidgets/src/osx/core/printmac.cpp:142: error: ‘PMPaperCreate’ was not declared in this scope' This is a PMPaperCreate is a deprecated function since Mac OS 10.5. PMPrinterGetPaperList should be used instead. There are two solutions: either install XCode 3.2 with Tiger (10.4) support enabled, or compile wxWdigets without 10.4 support:./configure -with-macosx-version-min=10.5 See Bug number 3: wxWidgets/src/osx/cocoa/textctrl.mm: In function 'void -wxNSTextFieldEditor keyDown:(wxNSTextFieldEditor., messagereft., NSEvent.)': wxWidgets/src/osx/cocoa/textctrl.mm:144: error: no matching function for call to 'wxWidgetImpl::FindFromWXWidget(objcobject.)' This is a bug in src/osx/cocoa/textctrl.mm, which was later fixed in subversion, and will be fixed in 2.9.1. See src/osx/cocoa/textctrl.mm solution: see attached patch and Bug number 4: ld: warning: in /System/Library/Frameworks//QuickTime.framework/QuickTime, missing required architecture x8664 in file This is due to the settings in the configure script.
Dji Assistant 2 For Mac
The QuickTime library is included is (($USEMAC and $USEDARWIN) or $USECOCOA) are set. If./configure is called with -with-osxcocoa, it seems that USEMAC and USEDARWIN are set, while USECOCOA is not set. This is utterly confusing, and since it is 'only' a warning, I did not look further in this matter. Libsdlmixer was upgraded on 10.5.8(ppc). The build result of wxWidgets(2.6.4&2.8.9&2.9.0) failed as follows.
$ sudo port -dv archive wxWidgets +universal g-4.0: -E, -S, -save-temps and -M options are not allowed with multiple -arch flags make:.pch/wxprecmonodll/wx/wxprec.h.gch Error 1 while executing 'commandexec build' (procedure 'portbuild::buildmain' line 9) invoked from within '$procedure $targetname' Warning: the following items did not execute (for wxWidgets): org.macports.archive org.macports.build org.macports.destroot Error: Status 1 encountered during processing. I just posted to the mailing list: Apparently this problem was fixed long ago by introducing a new port, called wxWidget-dev. Frankly, it is beyond me what the use is of a wxWidgets-dev, since packages like wxPython depends on wxWidgets and not on wxWidgets-dev, people can still not use the MacPorts solution and will get stuck anyway.
Lineage 2 For Mac
(sorry to sound a bit bitter here; It did of course compile the thing manually, but decided to spend a few hours testing it on different platforms, checking if all was OK and contributing back to the community. It really is quite frustrating to see that such good effort turns out to be fruitless because someone else solved it but did not bother to tell the world about it. That makes me wonder if I better had spend time on something else that on contributing to MacPorts.).
Hi all, I am working on porting an application I am working on from wxMac 2.6.2 to wxMac 2.8.6. It involves drawing of ellipses. After building and installing wxMac 2.8.6 the same way I did for wxMac 2.6.2 (./configure -disable-shared), I then just rebuilt my app changing the wx-confg to using 2.8 rather than 2.6. Well, it all built fine, but the y-axis 'seems' reversed. To facilitate debugging, I put some printf's into the DoDrawEllipse method for wxDC of Mac carbon. These printed just find under wxMac 2.6.2 but are not printing under 2.8.6.
I can see that wxGDC::DoDrawEllipse in common/dcgraph.cpp is being called (so I know the printf's in 2.8.6 work), but I have no idea where it is going from there. I'm pretty sure this is the root of my problem as code inspecing the Mac ellipse drawing code from 2.6.2 to 2.8.6 shows no significant changes. Anyone have an idea of what is getting called? You are correct regarding a new rendering engine.
It is controlled by a define: wxUSEGRAPHICSCONTEXT. You should be able to turn off the new rendering engine, and thereby fall back to the older engine, by using '-disable-graphicsctx' when running configure. However, that did not work for me (wxUSEGRAPHICSCONTEXT remains set to 1) so I manually forced wxUSEGRAPHICSCONTEXT to a value of 0. Even then, I am having some compilation issues I am currently working through. Hopefully, I'll be able to turn off the new rendering engine as it is not backward compatible with the previous one (at least for my application). You're looking at the wrong configuration option. The one you actually want for disabling the new Core Graphics rendering engine, and switching back to the Quick Draw engine (which has been deprecated btw), is by setting wxMACUSECOREGRAPHICS to '0'.
You can do this by editing include/wx/mac/carbon/chkconf.h, and rebuilding wxWidgets. The wxUSEGRAPHICSCONTEXT setting is specifically for the wxGraphicsContext classes, which have nothing to do with the wxDC classes other than that it's an alternative rendering API (and one which you aren't using if you're coming from 2.6). Dowty wrote:Having the wxUSEGRAPHICSCONTEXT option in setup.h is very misleading, since it can't be reset consistently here. I did an XCode project search for WXMACUSECOREGRAPHICS, but for unknown reasons it did not find it in the carbon version of chkconf.h. It's 'wxMACUSECOREGRAPHICS' (with a lowercase 'wx'), and it is in include/wx/mac/carbon/chkconf.h (on line 34 in my copy, should be the same in every version of 2.8). It's not in setup.h because it was never intended to be an option that users should change. It was meant to be a guard for controlling what version of wxWidgets it was going to be switched on just in case it wasn't ready for release.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |