-lPods not found issue in example project

[adamwaite]

-lPods not found issue in example project

[nemesis]

Do you reference the workspace when building?

[delebedev]

IMMEDIATE UPDATE: it happens because buildkit expects full path in :build_dir setting. Working on solution

[delebedev]

@nemesis sure I do :)

[delebedev]

Actually, I see use cases when :build_dir and other preferences can be both relative and absolute paths, so buildkit config should determine that and expand path to full if necessary (and leave 'as is' if it's already expanded).
Builds -> users/src/project/Builds
users/src/project/Builds -> users/src/project/Builds
@adamwaite what do you think? Should this pattern be applied to all options?

[adamwaite]

That would be great actually. Not sure how you might go about checking if the path is relative or absolute though? Unless you try finding relative and if it fails, try absolute, and if that also fails raise an exception? Can't think of a cleaner way to do it off the top of my head. I'm all for this though. Appreciate the help on this. Make a 'Contributors' section in the README and put yourself on there!

[delebedev]

If path starts with / its defenitely absolute one otherwise it's relative.
So basically workflow remains the same, but TaskRunnerConfig returns correct version of path and assertions work like before.

[adamwaite]

Haha of course, I think I need to go back to bed! Yes, that works.

[adamwaite]

Fixed with #14