On 17 Jun 2009, at 21:40, Joe Jones wrote:

So, is this a dead project now (Xcode bundle)?

Well, I did the bundle and I have moved away from Xcode project files (using CMake now).

But the problem you experience seems like it should be a simple fix. The Xcode template format is not documented and it seems a bit heuristic about how it goes about things, but effectively it is just running some files through a preprocessor using a set of preset variables, and from your error, it seems it just need to include one more variable for your template to expand without problems.

Which version of Xcode and what template were you expanding?

On Mon, Jun 15, 2009 at 7:27 AM, Joe Jones darkdescendant@gmail.com wrote:

...

When I attempt to create a new project called "Foo", I get the following error:

/tmp/temp_textmate.VmGETS:30:in 'read': No such file or directory - /Users/jjones/Documents/Code/Foo/ ___PROJECTNAMEASIDENTIFIER____Prefix.pch (Errno::ENOENT) /tmp/temp_textmate.VmGETS:30:in 'expand_file' /tmp/temp_textmate.VmGETS:94:in 'process' /tmp/temp_textmate.VmGETS:92:in 'each' /tmp/temp_textmate.VmGETS:92:in 'process' /tmp/temp_textmate.VmGETS:138

I see that the folder /Users/jjones/Documents/Code/Foo has been created and a bunch of projects are in there. Not sure what the issue is here and I was wondering if anyone here knows what to do to get around this?

Thanx, Joe

---

textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate

On 24 Jun 2009, at 17:37, Gerd Knops wrote:

On Jun 24, 2009, at 5:14 AM, Allan Odgaard wrote:

...

On 17 Jun 2009, at 21:40, Joe Jones wrote:

...

So, is this a dead project now (Xcode bundle)?

Well, I did the bundle and I have moved away from Xcode project files (using CMake now).

Even for Cocoa-based projects? How is that working?

Yes, and it works very well, but I had to write a lot of CMake support code to get to where I am now.

I have 3 essential “commands” which are CREATE_FRAMEWORK, CREATE_TOOL, and CREATE_APPLICATION. They create a framework, a CLI tool, and a bundled application. These take arguments for what to include in the build, e.g. my buffer.framework has the following definition:

CREATE_FRAMEWORK(buffer SOURCE_FILES src/*.cc PUBLIC_HEADERS src/buffer.h RESOURCES resources/* LINK_WITH scope LINK_WITH parse )

This is in a CMakeLists.txt file inside the ‘buffer’ folder containing the stuff for this framework (not sure if you are already familiar with CMake). Scope and parse are two other frameworks that the buffer framework is linked with.

As you can probably imagine, I feel that it is vastly superior working this way than having to maintain Xcode project files :) Also my commands pickup special extensions like ‘xib’ and do proper preprocessing — being in full control of this is nice (for example ANTLR generate two sources and a header for one grammar file, I don’t think I managed to get that working properly (with dependencies) in Xcode).

I have the TOOL/APP commands also crate a “Run«target name»” makefile target and I have setup this to be the default target and hence just use Make → Build (folder-specific variables are pretty useful for this, especially as they can reference TM_DIRECTORY).

I do feel my CMake files can be generalized more, but I attached them below incase you want to check it out. And while I much prefer this environment over Xcode files, CMake syntax is ghastly! Fortunately majority of the actual target-specific files are as simple as what’s shown above.

On 24 Jun 2009, at 20:30, Gerd Knops wrote:

[...] How do you debug? Besides the annoying maintaining of project files, this is pretty much the only function I use Xcode for, and the Debugger GUI is nice (compared to terminal).

I use a debugger so rarely that Terminal is fine. Litter your code with assertions and the need to debug it goes down dramatically, is my experience :)

Or can TM2 talk to the debugger?

It can’t.

[...] Also do you use git? I have modified the git part in the ProjectPlus plugin a lot so that it is much smarter about more complex project setups [...] Wonder if I should try and find the time to commit those changes.

I use Git, yes. If you have patches for how Project+ obtains status for files then you should publish these if you wish to see 2.0 have similar behavior ;)