Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pake unusable on windows after includes are using absolute path. #24

Open
Quasek opened this issue Apr 14, 2015 · 2 comments
Open

pake unusable on windows after includes are using absolute path. #24

Quasek opened this issue Apr 14, 2015 · 2 comments
Labels

Comments

@Quasek
Copy link
Contributor

Quasek commented Apr 14, 2015

As it says. Proposed solution is to switch to relpath.

@podusowski
Copy link
Owner

You mean #23 ? Give some details.

@Quasek
Copy link
Contributor Author

Quasek commented Apr 15, 2015

pake is trying to make a build directory for an object in the following way:

buildDir/TargetName/baseDirOfAbsolutePathToSourceFile.

And on windows it goes like:
C:...._build\Target\C:...\Source.o
which is not valid path on windows.

I made a workaround by adding:
in_filename = os.path.relpath(in_filename)
in __fetch_includes function

and by adding:
os.path.relpath(source_filename)
in object_filename function.

But this solution still does not solve a problem when sources files are in different directory tree than pake project.

@podusowski podusowski added the bug label Apr 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants