On Wed, 28 Mar 2018 11:05:49 -0400
"William L. Thomson Jr." wrote:
>
> cmake
> -C
> /tmp/portage/dev-util/efl-profiler-viewer-1.1/work/efl-profiler-viewer-1.1_build/gentoo_common_config.cmake
> -G Unix Makefiles -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_INSTALL_PREFIX=/
It was my fault. I was double s
Thanks for the reply
On Wed, 28 Mar 2018 08:46:51 +0200
Jérémy Zurcher wrote:
> Hi,
>
> what is the value of your env var $DESTDIR ?
> what is the value of -DCMAKE_INSTALL_PREFIX:PATH=$PREFIX when you
> invoke cmake ?
>
> it's all about these
> my cmake_install.cmake files are full of (PREFIX=
Hi,
what is the value of your env var $DESTDIR ?
what is the value of -DCMAKE_INSTALL_PREFIX:PATH=$PREFIX when you invoke cmake ?
it's all about these
my cmake_install.cmake files are full of (PREFIX=/opt/efl)
"$ENV{DESTDIR}/opt/efl/bin/efl_profiling_viewer"
"$ENV{DESTDIR}/opt/efl/lib/lib
Tried this again using make instead of ninja, the default cmake
generator. Which had no problems with generated the pot file so must
have been ninja specific. But I ran into install related issues.
l-profiler-viewer-1.1_build"
[ 3%] Generating pot
[ 7%] Built target time_interval_edj
[ 10%] Buil
On Tue, 26 Dec 2017 12:19:25 -0500
"William L. Thomson Jr." wrote:
> On Tue, 26 Dec 2017 12:09:41 -0500
> "William L. Thomson Jr." wrote:
>
> > cmake -G Ninja
> > ninja build
>
> cmake
> -C
> /tmp/portage/dev-util/efl-profiler-viewer-1.1/work/efl-profiler-viewer-1.1_build/gentoo_common_conf
On Tue, 26 Dec 2017 12:09:41 -0500
"William L. Thomson Jr." wrote:
> On Tue, 26 Dec 2017 12:03:30 +0200
> Mykyta Biliavskyi wrote:
> > If there are exists any issues with current cmake realisation - you
> > are welcome for a report this.
>
> This is an issue with the current build system. I
On Tue, 26 Dec 2017 12:03:30 +0200
Mykyta Biliavskyi wrote:
> Hi,
> Actually I haven't any plans about moving this project to use meson
> and ninja build system.
I am not suggesting to move to meson from cmake.
> Maybe someone from E devs could help with
> thing that you are reported, because p
Hi,
Actually I haven't any plans about moving this project to use meson and
ninja build system. Maybe someone from E devs could help with thing
that you are reported, because personally I didn't even try to setup
meson build system.
If there are exists any issues with current cmake realisation - y
Ran into a build issue, maybe ninja specific not sure. I switched all E
cmake based ebuilds over to ninja generator from autotools. Cmake
supports both autotools/make and ninja. Thus far I have yet to see any
build issues specific to ninja. Though I suspect this maybe one.
ninja: error:
'/tmp/port