How to compile my own framework scheduler

[HUO Jing <hu...@ihep.ac.cn>]

Dear all，

I wrote a framework scheduler with c++. But I don't know how compile it. 

please tell me how to compile my own framework scheduler and executor.

PS: why the long_lived_framework.cpp is included in Makefile, but after running the make command, there is no long_lived_framework.o or long_lived_framework?

Thanks.

Huojing from China

Re: Re: How to compile my own framework scheduler

[HUO Jing <hu...@ihep.ac.cn>]

Thank you very much !


Best Wishes !

在2013-11-26 02:43:50,HUO Jing<hu...@ihep.ac.cn>写道：
> After running make, the long_lived_framework binary is placed in the src
> directory of your build directory. However, this is a binary generated by
> libtool.
> 
> You will need to ensure the mesos headers: build/include/*.hpp are in your
> include path. These will need to be the built headers since the protobuf
> headers are only created after running 'make'.
> 
> You'll also need to link against libmesos. This will be installed in your
> library path after running make install, for example. (For me, this is
> /usr/local/lib).
> 
> Let me know if you run into any issues.
> 
> 
> On Mon, Nov 25, 2013 at 4:02 AM, HUO Jing <hu...@ihep.ac.cn> wrote:
> 
> > Dear all，
> >
> > I wrote a framework scheduler with c++. But I don't know how compile it.
> >
> > please tell me how to compile my own framework scheduler and executor.
> >
> > PS: why the long_lived_framework.cpp is included in Makefile, but after
> > running the make command, there is no long_lived_framework.o or
> > long_lived_framework?
> >
> > Thanks.
> >
> > Huojing from China
> >

Re: How to compile my own framework scheduler

[Benjamin Mahler <be...@gmail.com>]

After running make, the long_lived_framework binary is placed in the src
directory of your build directory. However, this is a binary generated by
libtool.

You will need to ensure the mesos headers: build/include/*.hpp are in your
include path. These will need to be the built headers since the protobuf
headers are only created after running 'make'.

You'll also need to link against libmesos. This will be installed in your
library path after running make install, for example. (For me, this is
/usr/local/lib).

Let me know if you run into any issues.


On Mon, Nov 25, 2013 at 4:02 AM, HUO Jing <hu...@ihep.ac.cn> wrote:

> Dear all，
>
> I wrote a framework scheduler with c++. But I don't know how compile it.
>
> please tell me how to compile my own framework scheduler and executor.
>
> PS: why the long_lived_framework.cpp is included in Makefile, but after
> running the make command, there is no long_lived_framework.o or
> long_lived_framework?
>
> Thanks.
>
> Huojing from China
>

Re: Re: How to compile my own framework scheduler

[HUO Jing <hu...@ihep.ac.cn>]

Thank you very mach !

在2013-11-26 00:34:14,HUO Jing<hu...@ihep.ac.cn>写道：
> Hi Huo,
> 
> If you have run `make install`, your library and include path just need to contain /usr/local/lib and /usr/local/include respectively.
> You can check your installation by looking for /usr/local/include/mesos and /usr/local/lib/libmesos.so (/usr/local/lib/libmesos.dylib on Mac).
> 
> You should be able to compile your framework and/or executor with:
> gcc -lmesos <your framework sources>
> 
> Alternatively, if you want to use a local build of Mesos. Use “-L” and “-I” to point to <build-directory>/src/.libs and <build-directory>/include/ respectively.
> 
> Cheers,
> Niklas
> 
> On Nov 25, 2013, at 4:02 AM, HUO Jing <hu...@ihep.ac.cn> wrote:
> 
> > Dear all，
> > 
> > I wrote a framework scheduler with c++. But I don't know how compile it. 
> > 
> > please tell me how to compile my own framework scheduler and executor.
> > 
> > PS: why the long_lived_framework.cpp is included in Makefile, but after running the make command, there is no long_lived_framework.o or long_lived_framework?
> > 
> > Thanks.
> > 
> > Huojing from China
>