nkpart / kit Goto Github PK

View Code? Open in Web Editor NEW

22.0 9.0 6.0 2.01 MB

Package manager type dealio for Objective-C

License: Other

Haskell 72.03% Shell 0.55% HTML 8.33% CSS 1.03% Objective-C 17.93% C 0.03% Makefile 0.09%

kit's Introduction

Kit

A dependency management tool for Obj-C/Xcode projects.

Install

$ brew install haskell-platform
# Make sure ~/Library/Haskell/bin is on your PATH. (~/.cabal/bin for older versions of the platform)
$ cabal install kit

Usage

See functionalkit for an example of a publishable dependency. The important part of it is the KitSpec file in the root. It follows a default structure.

Documentation is slowly emerging in the wiki.

kit's People

Contributors

Stargazers

Watchers

Forkers

whatupdave kimhunter davertay rkeniger johnmay10000 gabriella439

kit's Issues

Make the local repository directory configurable

Add upper bound to `errors` dependency

errors-2.0 will switch to use ExceptT instead of EitherT. If that will break your package then add an upper bound of errors < 2.0 to your dependencies.

Use force_load for sucking in categories

Any kits that contain categories need linker flags added to the master project to force loading of all members of static libraries. This is typically done with -all_load -ObjC on OTHER_LDFLAGS, but a nicer way is to use -force_load.

The exact directive required is -force_load $(TARGET_BUILD_DIR)/libKitDeps.a

It would be nice if the kit.xcconfig could somehow make this happen automatically. It may need to differentiate between it's own linker flags and those of the parent project.

kit --version wrong output

I've version 0.7.3 installed and output is 0.7.0

Allow the KitSpec filename to be passed on the command line

Following the rake/make conventions: kit -f ProductA.KitSpec

Add a Kit generator

Go beyond just creating a KitSpec, should create a full xcode project that builds a static lib as well. Might be able to use the current xcodeproj template?

Niiickkk, puullll myyyy puuullll reeeeqqqquuueesssstt!!!!!

#42

Prefix should be configurable in the kitspec

Add 'resolvers' for pulling kits from external sources

Resolvers can take a Kit (name + version) and potentially supply a thing that can be downloaded/copied into the local package cache.

2 forms: filesystem and http.

Add support for bundle targets

I think this needs to be completely specified in the KitSpec (ie. no default bundling).

eg.
source-directory: Source
bundles:
- name: Three20
directory: Three20.bundle

Switch over to some of Cabal's internals

This should give us version compatibility checking for free!

see the Distribution.Package and Distribution.Version modules

dev-packages kit not found if dep version isn't published

Kit requires that all dependencies are locally published before it looks for the kit in dev-packages. Although it will always use the kit in dev-packages.

Fix: check if the kit is in dev-packages before failing

say we've published
foo-0.0.1
foo-0.0.2

The kit file contains something like this.
name : bar
version : 1.0.0
"dependencies": [ { "name": "foo", "version": "0.0.3" } ]

And i have in dev-packages/foo

I get (although version number should be irrelevant)
kit error: Missing foo-0.0.3

Allow for source files to be filtered by a regex

I think the most useful thing would be an exclusion regex:

eg.
source-directory: "Classes"
source-exclude: "Test"

Can't override HEADER_SEARCH_PATH in a Kit

ASI needs this

not looking for kits in dev-packages

Allow for project-local dependencies

If a kit wanted to depend on a kit that wasn't in a repository, it should be able to do so. I'm thinking that the version field is dropped for these kits, in place of a path.

The path should point to either a kit package, or to a directory containing a specified kit.

See cabal-dev for something similar.

Syntax error in KitDeps.xcodeproj/project.pbxproj

Throughout project file 'sourceTree = "<absolute"' works by accident. Main side-effect is pre-compiler gets confused and throws up various warnings.

Kit 0.7.6 build fail

[17 of 19] Compiling Kit.CmdArgs ( Kit/CmdArgs.hs, dist/build/kit/kit-tmp/Kit/CmdArgs.o )

Kit/CmdArgs.hs:35:88: Not in scope: `versionArg'

Kit/CmdArgs.hs:35:116: Not in scope: `helpArg'
cabal: Error: some packages failed to install:
kit-0.7.6 failed during the building phase. The exception was:
ExitFailure 1

Barebone osx install + cabal update + cabal install + Xcode 4

Building yaml-0.4.1...
[1 of 1] Compiling Text.Libyaml ( Text/Libyaml.hs, dist/build/Text/Libyaml.o )
[1 of 1] Compiling Text.Libyaml ( Text/Libyaml.hs, dist/build/Text/Libyaml.p_o )

c/helper.c:1:20: error: stdlib.h: No such file or directory

c/helper.c:2:20: error: string.h: No such file or directory

c/helper.c:3:19: error: stdio.h: No such file or directory
In file included from c/helper.h:4,

             from c/helper.c:4:0:

c/yaml.h:149:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:308:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:438:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:735:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:988:0:
error: expected declaration specifiers or ‘...’ before ‘size_t’

c/yaml.h:989:0:
error: expected declaration specifiers or ‘...’ before ‘size_t’

c/yaml.h:1003:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:1095:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:1344:0:
error: expected declaration specifiers or ‘...’ before ‘size_t’

c/yaml.h:1357:0:
error: expected declaration specifiers or ‘...’ before ‘FILE’

c/yaml.h:1478:0:
error: expected declaration specifiers or ‘...’ before ‘size_t’

c/yaml.h:1561:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:1567:0:
error: expected specifier-qualifier-list before ‘FILE’

c/yaml.h:1693:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:1703:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:1715:0:
error: expected specifier-qualifier-list before ‘size_t’

c/yaml.h:1806:0:
error: expected declaration specifiers or ‘...’ before ‘size_t’

c/yaml.h:1819:0:
error: expected declaration specifiers or ‘...’ before ‘FILE’

In file included from c/helper.c:4:0:

c/helper.h:11:0:
error: expected declaration specifiers or ‘...’ before ‘size_t’

c/helper.c:12:0:
error: expected declaration specifiers or ‘...’ before ‘size_t’
c/helper.c: In function ‘buffer_append’:

c/helper.c:18:0:
error: ‘size’ undeclared (first use in this function)

c/helper.c:18:0:
error: (Each undeclared identifier is reported only once

c/helper.c:18:0: error: for each function it appears in.)

c/helper.c:22:0:
warning: implicit declaration of function ‘realloc’

c/helper.c:22:0:
warning: assignment makes pointer from integer without a cast

c/helper.c:28:0:
warning: implicit declaration of function ‘memcpy’

c/helper.c:28:0:
warning: incompatible implicit declaration of built-in function ‘memcpy’
c/helper.c: In function ‘get_parser_error_context’:

c/helper.c:56:0:
error: ‘yaml_parser_t’ has no member named ‘context’
c/helper.c: In function ‘get_parser_error_offset’:

c/helper.c:61:0:
error: ‘yaml_parser_t’ has no member named ‘offset’
c/helper.c: In function ‘get_scalar_length’:

c/helper.c:91:0:
error: ‘struct ’ has no member named ‘length’
c/helper.c: In function ‘get_scalar_tag_len’:

c/helper.c:103:0:
warning: implicit declaration of function ‘strlen’

c/helper.c:103:0:
warning: incompatible implicit declaration of built-in function ‘strlen’
c/helper.c: In function ‘get_scalar_style’:

c/helper.c:108:0:
error: ‘struct ’ has no member named ‘style’
c/helper.c: In function ‘yaml_parser_set_input_filename’:

c/helper.c:133:0:
error: ‘FILE’ undeclared (first use in this function)

c/helper.c:133:0:
error: ‘in’ undeclared (first use in this function)

c/helper.c:133:0:
warning: implicit declaration of function ‘fopen’

c/helper.c:135:0:
error: too many arguments to function ‘yaml_parser_set_input_file’
c/helper.c: At top level:

c/helper.c:138:0: error: expected ‘)’ before ‘*’ token
cabal: Error: some packages failed to install:
cmdargs-0.6.8 failed during the building phase. The exception was:
ExitFailure 1
data-object-yaml-0.3.3.5 depends on yaml-0.4.1 which failed to install.
kit-0.6.7 depends on yaml-0.4.1 which failed to install.
yaml-0.4.1 failed during the building phase. The exception was:
ExitFailure 1