Laurine: Xcode 10.2 error

Hello, this seems to be because Laurine is being run as a script; if you compile it to an executable in a separate step, then it’s fine:

Here’s my updated Run Script build phase:

set -x

# Get base path to project
BASE_PATH="$PROJECT_DIR/$PROJECT_NAME"

#--------- START OF YOUR CONFIGURATION (change Path_To_.. to fit)

# Get path to Laurine Generator script its the binary
LAURINE_PATH="$BASE_PATH/../scripts/LaurineGenerator.swift"
LAURINE_BIN_PATH="$BASE_PATH/../bin/laurine"

# Get path to main localization file (usually english).
SOURCE_PATH="$BASE_PATH/Base.lproj/Localizable.strings"

# Get path to output. If you use ObjC version of output, set implementation file (.m), as header will be generated automatically
OUTPUT_PATH="$BASE_PATH/Localizations.swift"

#--------- END OF YOUR CONFIGURATION

# Build laurine binary if necessary
if [ ! -f $LAURINE_BIN_PATH ]; then
env -i swiftc -emit-executable -o$LAURINE_BIN_PATH $LAURINE_PATH
fi

# Actually generate output. -- CUSTOMIZE -- parameters to your needs (see documentation).
# Will only re-generate script if something changed
if [ "$OUTPUT_PATH" -ot "$SOURCE_PATH" ]; then
"$LAURINE_BIN_PATH" -i "$SOURCE_PATH" -c -o "$OUTPUT_PATH"
fi

(env -i forces swiftc to run without Xcode environment variables - otherwise it tries to build an ARM binary)

cc @emilpedersen @lch88 @daaa57150 @ppth0608

Hey guys - Very long time no see. I have been helming my startup, https://supernova.io/ and it has been absolutely crazy - though it is something you might be interested in. That being said, I have definitely didn’t stop to observe this project and I have recently started fixing the issues and improving laurine in general. I expect that I could have the fixed version done and released within few days, so don’t lose hope - I’ll do my best to catch up.

Hope it helps some of you! 😃

Just to be clear, and based on @mflint and @alecmontgomery comments, here is the complete code:

set -x

# Get base path to project
BASE_PATH="$PROJECT_DIR/$PROJECT_NAME"

#--------- START OF YOUR CONFIGURATION (change Path_To_.. to fit)

# Get path to Laurine Generator script its the binary
LAURINE_PATH="$BASE_PATH/LaurineGenerator.swift"
LAURINE_BIN_PATH="$BASE_PATH/../bin/laurine"

# Get path to main localization file (usually english).
SOURCE_PATH="$BASE_PATH/App/Base.lproj/Localizable.strings"

# Get path to output. If you use ObjC version of output, set implementation file (.m), as header will be generated automatically
OUTPUT_PATH="$BASE_PATH/App/Localizations.swift"

#--------- END OF YOUR CONFIGURATION

mkdir -p $LAURINE_BIN_PATH

# Build laurine binary if necessary
if [ ! -f $LAURINE_BIN_PATH ]; then
env -i swiftc -emit-executable -o$LAURINE_BIN_PATH $LAURINE_PATH
fi

# Actually generate output. -- CUSTOMIZE -- parameters to your needs (see documentation).
# Will only re-generate script if something changed
if [ "$OUTPUT_PATH" -ot "$SOURCE_PATH" ]; then
"$LAURINE_BIN_PATH" -i "$SOURCE_PATH" -c -o "$OUTPUT_PATH"
fi

Just make sure the paths are ok. In my case, I have the app inside the “App” folder and so the paths have that. The mkdir command uses the variable $LAURINE_BIN_PATH created above.

I hope its clear for everyone.

Do you have any idea why it is executed like this and not the old way as it was working in xcode 10.1.1

I don’t know. I guess something has changed with the Swift interpreter, which means it cannot successfully parse/execute the Laurine script. But luckily it is able to compile the script into a binary, which we can then execute. ¯_(ツ)_/¯

@felipenandz

Your problem is that mkdir -p $LAURINE_BIN_PATH is making a directory with the name bin/laurine/, when it should just be making the directory bin/.

I’d change the script like this:

LAURINE_PATH="$BASE_PATH/../../LaurineGenerator.swift"
BIN_PATH="$BASE_PATH/../bin"
LAURINE_BIN_PATH="$BIN_PATH/laurine"

… and further down:

mkdir -p $BIN_PATH

Then the script will make bin/ directory, then compile the laurine binary into bin/laurine.

(You’ll also need to manually delete the directory bin/laurine/, before building for the first time)

Thanks mflint! It worked. I added mkdir -p $PROJECT_DIR/../Tools/Laurine/bin/ before # Build laurine binary if necessary to suppress an error about the bin directory not existing…

Same here 😃

I downloaded Xcode 10.1. In Xcode changed Command Line Tools to Xcode 10.1. With that setting I can run swift LaurineGenerator.swift -i Localizable.strings -c -o Localizations.swift in Terminal and it creates the Localizations.swift file fine. I use that as a workaround right now.