examples and install are both built by distcheck build, no need to also
build them in every other build
there's also no need to try building an app against the compiled libraries
since ci runs unit tests, requiring binaries to run after linking to the
libraries
Depends on D6662
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
mhm, i dont like this.
The install was done to get the *in the end* installed stuff tested with a client app, so we can ensure we have not broken apps due to header changes / missing headers, which is not happening on a normal pc as the removed headers will likely stay there. Its also a point where we could check the consistency of the installed eo files, i would really not remove this.
But it is not. Its done here for now. So cutting it out is just removing a feature we have in our CI...
Not removing, just moving:
https://travis-ci.org/Enlightenment/efl/jobs/412895146 grep testapp
When applying the pending patches the example app will be build during distcheck. https://phab.enlightenment.org/D6789
That part is covered now.
One thing to keep in mind is that we will later need to add make the install when we are going to extend the CI to build E and terminology as their builds will need to be based on the installed artifacts from the EFL build.
We do not have these builds right now and we still need to define in which jobs we are doing the install, etc. Just making sure we keep in mind that this need to be added back later in some form.