I am trying to build chrome on a macbook utilizing the tarball download. Its my understanding that after running gclient sync --force (takes 1 hour to complete), that gclient runhooks is issued to build the xcode project files. However, runhooks does nothing for me. The command is accepted, but it just returns back to the prompt instantaneously. No error and no result. Did I miss something for building? If anyone is wondering -- Im using this method because I cant use the SVN method.
Well, after a reboot, runhooks ran correctly and generated the xcode proj files. The issue is resolved. Must have been a glitch of some sort.
Related
So I am having this issue for the past 8-9 hours. I have been trying to resolve it by googling around.
This is what I have tried so far.
1) Totally uninstalled node and npm.
2) Totally uninstalled meteor. Deleted all the local/.meteor data. Searched for meteor in entire C drive and deleted it. Restarted the PC.
3) Reinstalled node, npm and meteor js again. (Did steps 1-3 in safe mode also and tried 3 times.)
4) Ran command and got this error again. "C:\Users\Admin\AppData\Local.meteor\packages\meteor-tool\1.4.4_2\mt-os.window
s.x86_32\dev_bundle\lib\node_modules\q\q.js:70
hasStacks = !!e.stack;
^
RangeError: Maximum call stack size exceeded".
Note: The same code works for me in another system, so apparently code is fine the issue is with meteor and my pc.
Then I found that creating new windows account and installing meteor there can make it work. So I tried to do that as well but no luck.
I need help to resolve this as I don't have any clue what to do next.
Meteor version is: 1.4
Node version is: 6.10.3
NPM version is: 3.10.10
Apologies for late response, just had the same problem and was eventually able to solve it. The problem is that windows doesn't like long file paths. Unfortunately, meteor is full of them so the installer seems to miss those files.
Try this:
Install meteor if its not already.
navigate to C:\Users\%username%\AppData\Local and delete the
.Meteor folder.
Download the installation archive:
https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.5/meteor-bootstrap-os.windows.x86_32.tar.gz
use 7-zip to extract the .Meteor folder somewhere with a shorter
path; ie: C drive root directory. Make sure you are running 7-Zip as
admin, and extract it using 7-Zips interface. Don't drag and drop as
this will extract to the temp folder first.
Go to your Environment Variables (in Control Panel/Advanced System
Settings), edit Path, and change the .Meteor directory to where you extracted the folder.
Open up CMD, cross your fingers, and enter meteor --version
Hope this helps any desperate souls out there.
I am having an issue where I do meteor run in my project, and it begins to install meteor-tool#1.4.0-1, once it is 100%, it says
Extracting meteor-tool#1.4.0-1...
but it never finishes. I uninstalled meteor and reinstalled it but I am having the same issue.
United State.
Windows 10.
This is a problem caused by the tar extractor provided by Git.
Find where is located the tar tool used by your system, running:
$ where tar
In my case, it is located in C:\Program Files\Git\usr\bin\tar.exe
Then locate the file and rename it to tar.exe.old
Its done... try running Meteor again! >> $ meteor
Thank you for your response, Vasil. I actually was able to find a solution and I am no longer experiencing this problem.
Turned out there was a problem with the tar.exe file in Git, and by uninstalling Git, and reinstalling it the latest version, 2.10.0.windows.1, the problem has seemed to go away.
It seemed that no matter how long I left it, it stayed stuck at "Extracting meteor-tools . . ." but now that I updated Git the problem has gone away.
Try adding the following to your local hosts file (C:\Windows\System32\Drivers\etc\hosts):
54.192.225.217 warehouse.meteor.com
Then run a meteor reset in your app directory (warning - will wipe your local DB), then try starting your app again.
This works for me.
Link: https://forums.meteor.com/t/downloading-meteor-tool-1-4-0-1/27269/19?u=lucianopestana
I was following the instruction from article https://github.com/thoughtbot/capybara-webkit/wiki/Installing-Qt-and-compiling-capybara-webkit for setting up an environment in my research of web automation. I'm using Windows installation case. Everything was perfect untill the point 11. When I type bundle exec rake build in my cmd I recieve this:
Command 'qmake CONFIG+\=test' not available.
I've read difficulties are not something unexpected at this step, so may be someone have seen this message before?
On windows after running the grunt build command for creating brackets shell it gives done without errors but i dont see any .exe file generated..
What might be the problem???
Here are some possible solutions:
Are you following the full brackets-shell build instructions, including all prerequisites?
Make sure Brackets isn't running at the same time. The build will fail silently if the .exe file is currently in use (see bug).
Try with a fresh git clone of the repo. If your brackets-shell local copy has been around for a while, sometimes the build & deps folders can get in a bad state. (I'm assuming you haven't modified the source at all. If you have, try with an unmodified copy of the source first to make sure it builds correctly without any of your changes).
Check that python --version shows 2.7.x
Verbose build output would also be helpful in diagnosing issues like this, but unfortunately there's not yet an easy way to get that...
If you follow the instructions on bracket-shell's wiki page, the Windows executable should be created in the Release directory.
I followed all the step is mention in given below url to build my project( I am using win7 OS).
https://github.com/adobe/brackets-shell/wiki/Building-brackets-shell.
actullly i want to create brackets installer (installed wix 3.7).
but i am getting cef-extract failed error.
even though i also used grunt cef-extract --force.
after that its throunging new error.
create -project failed after that i am not able to process further.
can some one help me.
thanks in advanced.
Regards
ashish .
If you include the exact console output you're seeing, it would be much easier to help you. But based on snags other people have encountered recently, you can try these things:
Make sure your PATH includes Python 2.7 (otherwise "create-project" will fail).
Delete all these folders to be sure you're starting from a clean slate: deps, Debug, include, libcef_dll, Release, Resources.
Just run the high-level tasks grunt setup and grunt build, following the Building brackets-shell instructions. (There's a known bug where grunt cef-extract fails when run standalone).