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

Fix for Node.js 0.6.0: Build seems to be now in Release instead of defaul #21

Merged
merged 2 commits into from
Nov 17, 2011

Conversation

mweibel
Copy link
Contributor

@mweibel mweibel commented Nov 7, 2011

Maybe you'll need to support backwards compatibility..

@astro
Copy link
Collaborator

astro commented Nov 10, 2011

Hmmm... IIRC I saw this issue during 0.5.x in another project. This fix breaks compatibility with node 0.4.x, right?

A symlink would probably the wrong solution, as node is great on Windows now. ;-)

@mweibel
Copy link
Contributor Author

mweibel commented Nov 10, 2011

I changed the patch to fix backwards compatibility (like @jorritd did it, but I used first "Release" because in future, more people will have >0.6.x as 0.4.x)

@ddopson
Copy link

ddopson commented Nov 17, 2011

+1 for mweibel's patch. That's the same code I wrote. It is 100% safe and should be merged in ASAP.

@c4milo
Copy link
Contributor

c4milo commented Nov 17, 2011

I was looking for some way to generate the symlink correctly with python-waf to avoid the try/catch hack but I couldn't find a more decent solution. +1 for this patch as a workaround.

astro added a commit that referenced this pull request Nov 17, 2011
Fix for Node.js 0.6.0: Build seems to be now in Release/ subdirectory instead of default/
@astro astro merged commit 30567d5 into xmppo:master Nov 17, 2011
@astro
Copy link
Collaborator

astro commented Nov 17, 2011

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants