Closed JefePapaya closed 7 years ago
hughsando
commented
8 years ago You could try removing the lines:
<flag value="-fmodules"/>
<flag value="-fcxx-modules"/>from iphonesim-toolchain.xml and iphoneos-toolchain.xml
If this works, I will see what I really need to do here.
Justinfront
commented
8 years ago with the circle no hxml example.
nme build iosview -Dsource-header=0 -DIPHONE_VER=9.3
eventually errors with.
Link : libApplicationMain.iphoneos-64.a
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't open file: bin/ios-view/haxe/cpp/ApplicationMain.iphoneos-v7.a (No such file or directory)
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't open file: bin/ios-view/haxe/cpp/ApplicationMain.iphoneos-64.a (No such file or directory)
For ios I get
Check dependencies
Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) were found.
\ BUILD FAILED ** But I don't know anything about ios so maybe I need some more stuff definded somewhere but assume the nme without hxml would work it's magic.
I was wondering if I wanted to embed cppia in textmate as a NSView what target should I use, I am kind of confused as how it all fits together and what I could do, is there a complete view project around that could be built with ninja rather than xcode. With textmate code I have managed to add a header bar below the tabs just above the normal textscroll area in textmate and compile it with ninja from terminal to show the file and file type currently open. So thought might be nice to embed nme as a view by merging the template nme ios controller with the controller I have in textmate. I presume I need a compiling iosview first before I can even think about how to implement this. Currently able to compile a normal iphone app in xcode, so presume my setup is ok but only have 9.3, running el-capitan all this obj-c / c stuff is pretty new but starting to follow some of it.
JefePapaya
commented
8 years ago @hughsando Thanks for your reply.
After commenting out the lines you said, the build worked! But still I had to use the command lime build ios -Dsource-header=0.
Justinfront
commented
8 years ago my tests above were with the lines commented out but used nme instead of lime, so even if I need to setup more stuff to get ios to work it looks like iosview is still broken?
Justinfront
commented
8 years ago ok seem to make some progress found the nmehost latest nme that helps but strangely when building for iosview I am gettting.
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't open file: Export/ios-view/haxe/cpp/ApplicationMain.iphoneos-v7.a (No such file or directory)
But the file and the libtool both seem to exist, I am now using the square example from NMML Test of the haxe website and compiles ok for iphonesim but not iosview or atleast as above fails on some steps.
Must admit I am really struggling to understand the iosview readme template instructions are they still correct for xcode 7.3 would like more of an overview of how the ::Class:: stuff connects up. I took the template from the nme iosview template folder but could not see any document folder. I understand the controller.mm stuff a bit it's how the bits fit together and the issues of getting a view together.
hughsando
commented
8 years ago The iosview template may need some attention. I am currently working on much better ios/hxcpp interop, which may make it a whole lot easier to write the iosview code, so I'm tempted to wait until I've finished that before revisiting this code.
Justinfront
commented
8 years ago Hugh
Some research links loosely related.
Have you been looking at _objectCBridgable? It would be nice to have much easier access to Haxe from swift, I say swift because having played with both it's far simpler for Haxers to code in swift than objective-c. https://github.com/apple/swift/blob/master/stdlib/public/core/BridgeObjectiveC.swift
There seems to be some movement to improve the Objective-C and swift bridge http://rosskimes.net/2016/07/Allow-Swift-types-to-provide-custom-Objective-C-representations/ https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160222/011032.html
Current use requires struts http://stackoverflow.com/questions/35893517/is-it-possible-to-replicate-swifts-automatic-numeric-value-bridging-to-foundatio https://www.netguru.co/blog/hidden-gems-swift http://nshint.io/blog/2015/10/07/easy-cast-with-_ObjectiveCBridgeable/ https://codedump.io/share/MTXoDWY3mnEA/1/is-it-possible-to-replicate-swifts-automatic-numeric-value-bridging-to-foundation-nsnumber-for-uint8163264-types
Xcode can actually convert suitable objective-c to swift https://developer.apple.com/library/ios/documentation/Swift/Conceptual/BuildingCocoaApps/MixandMatch.html
My swift / Objective-c knowledge is not very good. But this is certainly useful. https://github.com/programmingthomas/equivalent
Now there are a few attempts to extend the brigable concept for other languages. https://pypi.python.org/pypi/objp/1.3.2 http://opendylan.org/documentation/objective-c/#quick-usage
I don't know if a peg parser would help with creating stub code to connect with objective-c and swift.https://github.com/tondy67/abvkit
But ideally Haxe needs at the hxcpp or hl level a _bridgeable solution to an extent where users could tap into SceneKit, SpriteKit and GameKit by writting some structs, perahps it would even be possible to modify ObjectBridgeC.swift and actually have a version of swift that lets haxe users embed code. While it is nice to have NSView haxe it's also possible that embedding haxe logic into a swift app would also be useful. Sorry lots of thoughts and links but no code, but if one link is useful to you or someone else then my post will not be in vain.
hughsando
commented
8 years ago I will not be linking hxcpp to swift any time soon. But I have been looking at better hxcpp-objc-ios integration. If you write your code in haxe, it should not really matters what languages happen underneath, and objc++ is very close to hxcpp.
On Mon, Sep 12, 2016 at 4:59 PM, Justinfront notifications@github.com wrote:
Hugh
Some research links loosely related.
Have you been looking at _objectCBridgable? It would be nice to have much easier access to Haxe from swift, I say swift because having played with both it's far simpler for Haxers to code in swift than objective-c. https://github.com/apple/swift/blob/master/stdlib/ public/core/BridgeObjectiveC.swift
There seems to be some movement to improve the Objective-C and swift bridge http://rosskimes.net/2016/07/Allow-Swift-types-to-provide- custom-Objective-C-representations/ https://github.com/apple/swift-evolution/blob/master/proposals/0058- objectivecbridgeable.md https://lists.swift.org/pipermail/swift-evolution/ Week-of-Mon-20160222/011032.html
Current use requires struts http://stackoverflow.com/questions/35893517/is-it- possible-to-replicate-swifts-automatic-numeric-value-bridging-to-foundatio https://www.netguru.co/blog/hidden-gems-swift http://nshint.io/blog/2015/10/07/easy-cast-with-_ObjectiveCBridgeable/ https://codedump.io/share/MTXoDWY3mnEA/1/is-it-possible- to-replicate-swifts-automatic-numeric-value-bridging-to- foundation-nsnumber-for-uint8163264-types
Xcode can actually convert suitable objective-c to swift https://developer.apple.com/library/ios/documentation/Swift/Conceptual/ BuildingCocoaApps/MixandMatch.html
My swift / Objective-c knowledge is not very good. But this is certainly useful. https://github.com/programmingthomas/equivalent
Now there are a few attempts to extend the brigable concept for other languages. https://pypi.python.org/pypi/objp/1.3.2 http://opendylan.org/documentation/objective-c/#quick-usage
I don't know if a peg parser would help with creating stub code to connect with objective-c and swift.https://github.com/tondy67/abvkit
But ideally Haxe needs at the hxcpp or hl level a _bridgeable solution to an extent where users could tap into SceneKit, SpriteKit and GameKit by writting some structs, perahps it would even be possible to modify ObjectBridgeC.swift and actually have a version of swift that lets haxe users embed code. While it is nice to have NSView haxe it's also possible that embedding have logic into a swift app would also be useful. Sorry lots of thoughts and links but no code, but if one link is useful to you or someone else then my post will not be in vain.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HaxeFoundation/hxcpp/issues/504#issuecomment-246288308, or mute the thread https://github.com/notifications/unsubscribe-auth/ABlp1pgU_lKfNbbrV_mN4TioykZIbNq8ks5qpRR_gaJpZM4JxwC- .
There's already a discussion about these issues, but it's in the HaxeFlixel repository: https://github.com/HaxeFlixel/flixel/issues/1863#issuecomment-243535580
I've managed to build the same project successfully with hxcpp version 3.3.49 using
lime build ios -Dsource-header=0 -DIPHONE_VER=9.3With the hxcpp built from the commit mentioned above, if I try to build using
lime build ios, I get:Just like mentioned in the HaxeFlixel's issue #1863.
Then, applying the solution given there, if I use
lime build ios -Dsource-header=0, I'm able to get further in build process, but it ultimately fails with the error:On the bright side, it seems the wrong definition of
IPHONE_VERproblem was fixed.