I am working on a project for which we will be using ParseKit. Currently I have no access to a Mac, but want to start working on some initial testing and parsing for an application on Ubuntu.
I would assume this should require no more than a console app to test some parsing with ParseKit, but maybe it's more complicated than that.
I have GNUstep installed and can compile an Objective-C program with a GNUmakefile (allowing me to use #import <Foundation/Foundation.h> and all the 'NS' objects).
Is it possible to compile and run a project along with ParseKit without XCode on Ubuntu? If it is possible then how would I go about this? Do I need to move the ParseKit source files to a specific folder or change the source in any way? Do I need to include all the ParseKit files in the makefile?
Any help is appreciated. Thanks.
As far as I can tell you is that you cannot build ParseKit with GNUstep Foundation alone, at least not without some source modifications, that may include trying to install gnustep-corebase for CoreFoundation types. You will also need to bypass OS-specific headers like TargetConditionals.h or AvailabilityMacros.h. I am not sure how much hacks you will need to make the original source more portable. If this really worth it you will have to write a simple GNUmakefile, so you can start compiling the project and fix things.
Related
I have a npapi plugin(bundle) for chrome, which use C++ and objective-c. now it needs to be build by google native client.
I wonder that can nacl support objective-c? how to compile o-c file by MakeFile
And if possible, how to build nacl plugin in Xcode? I tried, but i found that the libraries of nacl are " archive with no architecture specification".(use lipo -info *.a)
I hope someone to help me, thanks a lot!!!
If you use Objective-C without any of its usual libraries then you should be able to use the PNaCl toolchain (which is based on LLVM) to have it parse Objective-C. I'm not aware of projects that have done this, so you should definitely let folks on the mailing list know if you get something working (do keep the questions on SO, though!).
It sounds like your application won't be running on the open web (where only architecture-independent PNaCl can run, not NaCl), so you could either use the PNaCl toolchain to create a .pexe, or you could use the same toolchain to create a .nexe for each architecture you target. The documentation I linked to helps with both approaches, but note that using the PNaCl toolchain to create a .nexe is currently being improved. You can therefore follow the instructions on the bug tracker, or try out nacl-clang when it's released (or build it yourself if you're brave).
how can I utilise the sqlite3.h from sqlite.org in my programs written in xCode 5.1.1?
One of the ways I was thinking was to download the precompiled binaries for Max OSX, http://www.sqlite.org, and then link them somehow to my files in my xCode-project.
How can I link these binaries to my project or xCode so that I can call upon the different sqlite3-functions?
Any help is much appreciated. I have OSX version 10.9.4.
The recommended way to use SQLite is to compile it statically into your program, i.e., just add the sqlite3.c file to your other source files.
I'd like to know if it is possible to get a list of the frameworks being used in an Objective-C project.
Perhaps there's some way to access XCode's "Build Phases"? Doesn't matter if it's some obscure method not advised by Apple, I'm trying to make an XCode plugin.
Thanks
I haven't written a Xcode plugin (yet), but is there a way for you to use terminal commands? If this is possible you could open the projects build path and simply use
ls *.framework
They should also be linked in the .xcodeproj file.
I'm creating a modular open-source library. Let's say the project has 15 .m files in it.
Should I (1) release it like the Venmo iOS SDK (Cocoa Touch Static Library) or (2) release it like JSONKit (just the source code)?
Releasing as source code means you, and your developers, don't have problems when a new architecture comes out. A static library built as armv6 wouldn't work with the latest Xcode today.
One caveat with source code releases, since you don't know what build settings the project it's added to will have, you'll need to do extra work to make sure it builds without warnings as best you can, even for pedantic warnings.
I prefer frameworks over static libs. Its easier to ship resources in the framework bundle if you eventually need to and there no cost to dynamic linking. If its pure C and the libraries dependencies are guaranteed to be there then it might be ok. But in general I try to avoid static linking unless I know the target OS has the exact dependencies for that binary at deployment time.
Its much easier to load a dynamic library with the endpoints you need at runtime (which were compiled for that exact platform but have the same external interface) than it is to fail with a static lib that was compiled directly to external dependencies which dont exist on the target platform.
Maybe Im crazy but this is what Ive always done in C, C++ or obj C. Just my opinion.
http://en.wikipedia.org/wiki/Static_library
I really need a static version of the DevIL DLLs for windows as I need to statically link my program to it. Anyone got one?
I, unfortunately, don't have the toolchain to compile from source :/
thanks,
Is there some particular reason you can't (or are unwilling) to get the necessary toolchain to compile it?
That said, what's wrong with the material available from the download page? All the libs you need to compile are listed right there at the end, and there's an MSVC++ 2008 package all zipped up to make it even easier.
http://openil.sourceforge.net/download.php