-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
How to build codeception.phar? #1197
Comments
You need robo task runner and run |
Could be documented somehow. |
It is see 2 latest lines on a page :) As you asked it is documented somehow ) |
That's a good enough hint, I think. |
@DavertMik is there any reason to worry about the following output after running
? Codecept.phar got still created and first short try running the interactive console looks also promising. |
In 2.0.10, if I go into the vendor/codeception/codeception folder and run robo build:phar I get:
It is calling
Which suggests that I should running it from the root folder above vendor but I cannot run it from the command from the root folder. I am either missing something in the install instructions or something else. If I point it to a relative path it builds codecept.phar but then cannot compile it. I have not logged this as a bug because the error suggest something I am doing wrong or I interpreted the install instructions incorrectly. |
clone this repo and run robo.phar in the main directory of it. |
@Naktibalda . Thanks. Will try that. |
Robo will still be looking for DIR.'/vendor/autoload.php'; in RoboFile.php and this path does not exist relative to the main directory. Have I completely missed something fundamental here? |
composer install |
Codeception was installed using 'composer install' into the /vendor directory but, as I wrote in the original post, RoboFile.php is trying to load relative path DIR.'/vendor/autoload.php'.
|
How can I build codeception.phar from current branch?
I saw in commit log that the interactive console will be fixed in 2.0.3 but want to test it before 2.0.3 now if possible.
Thanks
The text was updated successfully, but these errors were encountered: