owensd / apous Goto Github PK

Add support for nest folders as packages and package dependencies.

main.swift
    io/
        path/
    sys/

Each of the folders could be packages and/or dependencies, and most importantly, not require and Xcode project to build.

Currently only OS X is supported for the script; support iOS too.

The CLI interface is a hack, needs to have proper support for commands:

apous update
apous help
apous run [path/to/scripts]
apous edit
apous init

etc...

A script that hasn't changed shouldn't need to be recompiled. Make sure this recompile isn't happening.

For example, if I were to create a file called main.swift and fill it with:

#!/usr/local/bin/apous
print("Hello, World!")

then executing the following:

$ chmod +x main.swift
$ ./main.swift

Would simply output

Hello, World!

However, if I were to rename it to just main, or main1.swift, it starts throwing errors:

$ ./main
<unknown>:0: error: no input files

$ ./main1.swift
Only a 'main.swift' file can be specified.

If I wanted to, for example, have a build script created through apous, calling the file main.swift would be sort of ridiculous, setup or install makes much more sense.

Just a few thoughts - I really like apous either way 👍

I've got Carthage installed but I haven't used it enough to know what this is referring to in particular.

This would help by allowing scripters to use Xcode to edit the scripts without actually requiring projects to be built and maintained.

It may be advantageous to be able to store scripts in nested folders.

main.swift
    /utils
        util1.swift
        util2.swift

Currently, these will be ignored. This will likely tie into issue #2 as we think about free-floating packages that are not tied to an Xcode project.

I created the following script:

#!/usr/local/bin/apous

import Foundation
import CommonMark
import LiterateSwift

print("Hello")

And the following Podfile:

platform :osx, 10.9

plugin 'cocoapods-rome'

use_frameworks!

pod 'CommonMark'
pod 'LiterateSwift'

However, when I run it, I get the following error (regardless of whether I take the hasbang approach or compile everything).

<unknown>:0: error: cannot load underlying module for CoreGraphics
<unknown>:0: note: did you forget to set an SDK using -sdk or SDKROOT?
<unknown>:0: note: use "xcrun -sdk macosx swift" to select the default OS X SDK installed with Xcode

Maybe add it to homebrew or just have a simple script that can be run.

I think the only real consideration here is Xcode.app and Xcode-beta.app. Supporting arbitrary versions of Swift seems like something that wouldn't even be feasible.

Maybe mark scripts as requiring at least a particular version of Swift? Still problematic as Swift is still not source-compatible between versions yet.

In the title.

OMG!