-
Notifications
You must be signed in to change notification settings - Fork 19
Compass will not build (exit code 255) #59
Comments
Hi @raduluchian. So as I understand, you get the exact same error in the same project on both machines, independent of the OS you're running. Sounds like the project setup is wrong for the the build system first instance. But lets try to get some more details. What does your compass config (config.rb) looks like? It should be stored in the root folder of your project. Also, did you try to compile via console & terminal with a raw compass command? |
Sorry for not being more clear on the last part. The same project is working on my Linux Mint machine (office) but it's not working on my Windows 8.1 machine (home). The config file is the same on both machines. I haven't tried compiling via terminal yet but I have successfully compiled using Compass.app. I will share the config.rb file this evening. |
Is it possible that it could be related to backslashes #58 on Windows? I'm not sure Compass.app takes the config.rb or maintaining its own configuration. |
I will try looking into the backslashes as well. As far as the config.rb file goes, I know that Compass.app uses the file found in the root of the project and if it's not there it throws an error. |
These are the contents of my config.rb file:
|
Can you try to run the compass command directly from the console on your Windows machine? Of course in your project root folder.
I would like to find out if it's related to the package or your environment. And I still think, the Compass.app includes compass itself and does not rely on the local installation of the compass gem. |
Just tried compiling from the comand line as you suggested and it works fine. |
So my next guess is, the path of your project contains some special chars and the windows batch seems to have problems with them in the for-loop. That's also what I see in the stackoverflow thread. Do you have special chars like brackets or braces in your path? If yes, could you try to move your project to a more generic path and test it again? Good
Bad
|
Indeed the issue was in the project path. The name of the folder used to be:
After having done a bit of restructuring I've renamed it into:
Now the code is compiled as expected, so I have a working plugin that does it's job properly. Thanks a lot for the patience and help, René! Is there however a way to have it work with paths such as the one I originally had? |
The batch file of this package uses a for loop to loop trough a list of folders or files. This part may have to be encoded correctly to work with all path. I'm not a windows batch pro. But what I found is, that the So you could try to edit the batch file (Preferences → Browse Packages, then go to the Compass folder) and change the I didn't tested it. No clue if it works and if it solves the problem and when, if it solves it for all path. It's worth a try. Anyway, I will add your case to the F.A.Q. in the readme. |
Ok, will look into it to see if that solution works. Thanks for the help! |
I have this plugin installed in Sublime Text 3 and whenever I want to build I get this in the console:
This issue has been described by someone else on Stack Overflow, but with no resolution:
http://stackoverflow.com/questions/25229159/sass-compass-will-not-build-exit-code-255-sublime-text-3#comment49709536_25229159
It's worth mentioning that I am running the same configuration at home as at the office with the difference that at the office I am running on Linux Mint and at home on Windows 8.1.
The text was updated successfully, but these errors were encountered: