GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Quick, short summary:
There are 2 places (spots) to specify the output folder for LESS, which – in my setup – cancel each other out.
My Setup is somehow strange – don’t ask, I entered a team at an existing project (doh) – and these guys don’t work with CodeKit, so I have to adapt their setup – it’s an project based on bootstrap:
Both settings respect each other
Both settings cancel each other out
Exact steps to reproduce:
A link to download a simplified project or file that shows the issue:
Your configuration (any details about your system that you think might be relevant)
Have you read the Output Paths & Actions section of codekitapp.com/help/? If not, start there. I'm having trouble following your exact problem, but here's what I can tell you:
When you apply Output Paths from Project Settings, that overwrites anything you've specified on a file-by-file basis. That's correct behavior.
It sounds like all you need to do is select _main.less, choose Change, then go over to your Vendor folder and name the file styles.css.
I'm not sure why you're worried about source map paths. You WANT relative paths in the map and CodeKit will always create relative paths in the sources array. Changing the option in Project Settings to "relative to the project root folder" will have no effect on paths in the source map. Those are calculated automatically by the Less compiler and they're always relative.
I'm also unable to reproduce the issue in Step 5. When I return to Project Settings, the Output Path option is still listed as relative to the project root folder.