You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@celix.apache.org by Roddie Kieley <rk...@gmail.com> on 2013/06/19 14:58:47 UTC
Introduction
Hi folks, just wanted to say a quick hello after hearing about Celix
from Jamie Goodyear, of Karaf, when he mentioned it during one
of our study group meetings recently where the subject was OSGi.
My development background is primarily native c++/c/obj-c,
decreasing in that order, although I've also worked on the support
side in Java land with OSGi as well as completed a few years of
work life in the c#/vb .NET land.
At the moment I'm looking at spending some time developing
Celix as I'd like to use it to manage the lifecycle and modularization
of a back-end game server I've been working on the last little
bit. As such, I've made some first minor changes to the
CMakeLists.txt files adding a few lines to a few of the list files
so that the included headers would show up properly in the
generated Xcode project, which is my tool of choice at the
moment. See attached for a patch if it's of any interest.
Looking forward to hearing more about the upcoming
mini-hackathon and where I could potentially focus my
efforts to best help the community.
Roddie Kieley
twitter.com/RoddieKieley
Re: Introduction
Posted by Karl Pauls <ka...@gmail.com>.
On Mon, Jun 24, 2013 at 3:17 PM, Alexander Broekhuis
<a....@gmail.com>wrote:
> Hi,
>
>
> 2013/6/19 Roddie Kieley <rk...@gmail.com>
>
> > Hi Alexander, thanks for the welcome. Not sure what happened with the
> > patch, I double checked my sent mail and I had attached it. Either way
> > I have since created "Celix-72: 'Header Files' sub folder not included
> in
> > all folders in generated Xcode project' and attached the patch there.
> >
>
> As far as I know this list should accept attachments..
>
I don't think it does. The way to get small stuff to an apache project is
to attach it to a jira issue (mainly because there you mark it as a grant).
regards,
Karl
> I have applied the patch, haven't tested it on windows yet, but this will
> probably only make it better. Visual Studio also expects all header files
> to be explicitly listed.
>
>
> >
> > I am indeed using Xcode, and it apparently uses the Clang C, C++,
> > Obj-C, and Obj-C++ front-end for the LLVM compiler. Most of my
> > usage has been C++/Obj-C++ but it looks like C/Obj-C is also
> > no problem, which has been my experience with Celix thus far.
> >
>
> I use Eclipse on OSX, so I already use Clang etc. It gives better/more
> warnings then GCC does, but not all of them have yet been fixed ;).
> How did you instrument CMake to make XCode project files? I'd like to test
> it a bit, and possibly add some info to the Celix page.
>
>
> >
> > As such, the discussion surrounding a wrapped and/or native C++
> > implementation is of interest and I will review the attached
> > links to get up to speed. Wrt Remote Services will keep my
> > eye out for more information on the specific goals of the weekend
> > and see if there's an area I can make a contribution to remotely.
> >
>
> Good to hear, if you have any remarks/ideas/etc feel free to post them!
>
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis
>
--
Karl Pauls
karlpauls@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls
Re: Introduction
Posted by Roddie Kieley <rk...@gmail.com>.
Hi Alexander. I just checked out the latest source and apart from the
seemingly unrelated problem I raised in CELIX-73 [1], having a
directory structure of:
./celix (the checked out source
./celix-build (where 'ccmake ../celix -GXcode' is run)
appears to work as well as having the 'build' directory inside the 'celix'
directory.
While I haven't used CMake extensively as a developer it seems to do
a competent job of integrating the respective IDE's into a cross-platform
build system.
Roddie...
--
[1]: https://issues.apache.org/jira/browse/CELIX-73
On Wed, Jun 26, 2013 at 3:43 AM, Alexander Broekhuis
<a....@gmail.com>wrote:
> Hi,
>
> 2013/6/26 Roddie Kieley <rk...@gmail.com>
> >
> >
> > To customize the setup I ended up using 'ccmake .. -GXcode' to use the
> > ncurses interface and turned all the 'BUILD_*' items to 'ON'. Note that I
> > also have had MacPorts on my machine for quite some time so using the
> > configure option it found most everything it required - see
> > http://pbrd.co/14qmyKz for a screenshot of page 1 of the ncurses ccmake
> > interface.
> >
>
> The default way to create the project/make files is to use ccmake, so the
> use of the ncursus is actually intended to enable/disable parts. I thought
> the website was already updated for this, but it is actually really
> outdated! The BUILDING file is up to date and explains the process detailed
> enough (imho) [1]. I'll raise a bug for the lacking documentation on the
> website.
>
> There is one difference wrt how you build, the described method has a build
> directory on the same level as the project directory, eg a "celix-build" in
> the same directory as the "celix" directory. The reason for this has to do
> with how Eclipse handles projects/binaries/sources etc. Is this a problem
> for XCode, or does this work as well? If so, I can easily extent the
> BUILDING file with an additional line for the Xcode support.
>
>
> > At that point it was just a matter of generating and opening up the
> > resultant Celix.xcodeproj to do a build. Pretty sure at this point
> > everything else worked as it should.
> >
> >
> Good to hear! I am more and more convinced that CMake was to right tool to
> start with. Make support, Eclipse project files generation, Visual Studio
> project files generation, and now also XCode support :D.
>
>
> >
> > > Alexander Broekhuis
> > >
> >
>
> [1]: http://svn.apache.org/repos/asf/incubator/celix/trunk/BUILDING
>
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis
>
Re: Introduction
Posted by Alexander Broekhuis <a....@gmail.com>.
Hi,
2013/6/26 Roddie Kieley <rk...@gmail.com>
>
>
> To customize the setup I ended up using 'ccmake .. -GXcode' to use the
> ncurses interface and turned all the 'BUILD_*' items to 'ON'. Note that I
> also have had MacPorts on my machine for quite some time so using the
> configure option it found most everything it required - see
> http://pbrd.co/14qmyKz for a screenshot of page 1 of the ncurses ccmake
> interface.
>
The default way to create the project/make files is to use ccmake, so the
use of the ncursus is actually intended to enable/disable parts. I thought
the website was already updated for this, but it is actually really
outdated! The BUILDING file is up to date and explains the process detailed
enough (imho) [1]. I'll raise a bug for the lacking documentation on the
website.
There is one difference wrt how you build, the described method has a build
directory on the same level as the project directory, eg a "celix-build" in
the same directory as the "celix" directory. The reason for this has to do
with how Eclipse handles projects/binaries/sources etc. Is this a problem
for XCode, or does this work as well? If so, I can easily extent the
BUILDING file with an additional line for the Xcode support.
> At that point it was just a matter of generating and opening up the
> resultant Celix.xcodeproj to do a build. Pretty sure at this point
> everything else worked as it should.
>
>
Good to hear! I am more and more convinced that CMake was to right tool to
start with. Make support, Eclipse project files generation, Visual Studio
project files generation, and now also XCode support :D.
>
> > Alexander Broekhuis
> >
>
[1]: http://svn.apache.org/repos/asf/incubator/celix/trunk/BUILDING
--
Met vriendelijke groet,
Alexander Broekhuis
Re: Introduction
Posted by Roddie Kieley <rk...@gmail.com>.
To instrument CMake to make the XCode project I tried a simple 'mkdir
build; cd build; cmake .. -GXcode' from the celix directory but that didn't
include everything and at the time I had originally wanted to take a look
at the shell project after looking at a related issue in JIRA.
To customize the setup I ended up using 'ccmake .. -GXcode' to use the
ncurses interface and turned all the 'BUILD_*' items to 'ON'. Note that I
also have had MacPorts on my machine for quite some time so using the
configure option it found most everything it required - see
http://pbrd.co/14qmyKz for a screenshot of page 1 of the ncurses ccmake
interface.
At that point it was just a matter of generating and opening up the
resultant Celix.xcodeproj to do a build. Pretty sure at this point
everything else worked as it should.
Roddie...
On Mon, Jun 24, 2013 at 10:47 AM, Alexander Broekhuis <a.broekhuis@gmail.com
> wrote:
> Hi,
>
>
> 2013/6/19 Roddie Kieley <rk...@gmail.com>
>
> > Hi Alexander, thanks for the welcome. Not sure what happened with the
> > patch, I double checked my sent mail and I had attached it. Either way
> > I have since created "Celix-72: 'Header Files' sub folder not included
> in
> > all folders in generated Xcode project' and attached the patch there.
> >
>
> As far as I know this list should accept attachments..
> I have applied the patch, haven't tested it on windows yet, but this will
> probably only make it better. Visual Studio also expects all header files
> to be explicitly listed.
>
>
> >
> > I am indeed using Xcode, and it apparently uses the Clang C, C++,
> > Obj-C, and Obj-C++ front-end for the LLVM compiler. Most of my
> > usage has been C++/Obj-C++ but it looks like C/Obj-C is also
> > no problem, which has been my experience with Celix thus far.
> >
>
> I use Eclipse on OSX, so I already use Clang etc. It gives better/more
> warnings then GCC does, but not all of them have yet been fixed ;).
> How did you instrument CMake to make XCode project files? I'd like to test
> it a bit, and possibly add some info to the Celix page.
>
>
> >
> > As such, the discussion surrounding a wrapped and/or native C++
> > implementation is of interest and I will review the attached
> > links to get up to speed. Wrt Remote Services will keep my
> > eye out for more information on the specific goals of the weekend
> > and see if there's an area I can make a contribution to remotely.
> >
>
> Good to hear, if you have any remarks/ideas/etc feel free to post them!
>
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis
>
Re: Introduction
Posted by Alexander Broekhuis <a....@gmail.com>.
Hi,
2013/6/19 Roddie Kieley <rk...@gmail.com>
> Hi Alexander, thanks for the welcome. Not sure what happened with the
> patch, I double checked my sent mail and I had attached it. Either way
> I have since created "Celix-72: 'Header Files' sub folder not included in
> all folders in generated Xcode project' and attached the patch there.
>
As far as I know this list should accept attachments..
I have applied the patch, haven't tested it on windows yet, but this will
probably only make it better. Visual Studio also expects all header files
to be explicitly listed.
>
> I am indeed using Xcode, and it apparently uses the Clang C, C++,
> Obj-C, and Obj-C++ front-end for the LLVM compiler. Most of my
> usage has been C++/Obj-C++ but it looks like C/Obj-C is also
> no problem, which has been my experience with Celix thus far.
>
I use Eclipse on OSX, so I already use Clang etc. It gives better/more
warnings then GCC does, but not all of them have yet been fixed ;).
How did you instrument CMake to make XCode project files? I'd like to test
it a bit, and possibly add some info to the Celix page.
>
> As such, the discussion surrounding a wrapped and/or native C++
> implementation is of interest and I will review the attached
> links to get up to speed. Wrt Remote Services will keep my
> eye out for more information on the specific goals of the weekend
> and see if there's an area I can make a contribution to remotely.
>
Good to hear, if you have any remarks/ideas/etc feel free to post them!
--
Met vriendelijke groet,
Alexander Broekhuis
Re: Introduction
Posted by Roddie Kieley <rk...@gmail.com>.
Hi Alexander, thanks for the welcome. Not sure what happened with the
patch, I double checked my sent mail and I had attached it. Either way
I have since created "Celix-72: 'Header Files' sub folder not included in
all folders in generated Xcode project' and attached the patch there.
I am indeed using Xcode, and it apparently uses the Clang C, C++,
Obj-C, and Obj-C++ front-end for the LLVM compiler. Most of my
usage has been C++/Obj-C++ but it looks like C/Obj-C is also
no problem, which has been my experience with Celix thus far.
As such, the discussion surrounding a wrapped and/or native C++
implementation is of interest and I will review the attached
links to get up to speed. Wrt Remote Services will keep my
eye out for more information on the specific goals of the weekend
and see if there's an area I can make a contribution to remotely.
Roddie...
On Wed, Jun 19, 2013 at 10:41 AM, Alexander Broekhuis <a.broekhuis@gmail.com
> wrote:
> Hi Roddie,
>
> 2013/6/19 Roddie Kieley <rk...@gmail.com>
>
> > Hi folks, just wanted to say a quick hello after hearing about Celix
> > from Jamie Goodyear, of Karaf, when he mentioned it during one
> > of our study group meetings recently where the subject was OSGi.
> >
>
> Welcome to Celix! An extra pair of eyes is always welcome!
>
>
> > At the moment I'm looking at spending some time developing
> > Celix as I'd like to use it to manage the lifecycle and modularization
> > of a back-end game server I've been working on the last little
> > bit. As such, I've made some first minor changes to the
> > CMakeLists.txt files adding a few lines to a few of the list files
> > so that the included headers would show up properly in the
> > generated Xcode project, which is my tool of choice at the
> > moment. See attached for a patch if it's of any interest.
> >
>
> Did you perhaps forget to attach the patch? Either way, the preferred
> method for patches/issues is our Jira project at [1]. If you could create
> one or more issues over there and attach the patches I will take a look and
> see if there are any problems wrt Eclipse etc.
>
> Out of curiosity, you are using XCode? Does it handle C properly? If so, I
> think it would be a nice addition to our supported IDE's!
>
>
> >
> > Looking forward to hearing more about the upcoming
> > mini-hackathon and where I could potentially focus my
> > efforts to best help the community.
> >
>
> Do you have any specific area where your interests are? I guess/hope that
> the hackathon will focus on Remote Services. Another area which is rather
> new, but also interesting, is Native-OSGi and the specification work we
> want to start on. See [2] and [3] for some more info.
>
> Thanks for your interest!
>
> [1]: http://issues.apache.org/jira/browse/CELIX
> [2]: http://incubator.markmail.org/thread/jbv7ytketpms56hc
> [3]: http://blog.cppmicroservices.org/2013/06/14/native-osgi-rfp/
>
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis
>
Re: Introduction
Posted by Alexander Broekhuis <a....@gmail.com>.
Hi Roddie,
2013/6/19 Roddie Kieley <rk...@gmail.com>
> Hi folks, just wanted to say a quick hello after hearing about Celix
> from Jamie Goodyear, of Karaf, when he mentioned it during one
> of our study group meetings recently where the subject was OSGi.
>
Welcome to Celix! An extra pair of eyes is always welcome!
> At the moment I'm looking at spending some time developing
> Celix as I'd like to use it to manage the lifecycle and modularization
> of a back-end game server I've been working on the last little
> bit. As such, I've made some first minor changes to the
> CMakeLists.txt files adding a few lines to a few of the list files
> so that the included headers would show up properly in the
> generated Xcode project, which is my tool of choice at the
> moment. See attached for a patch if it's of any interest.
>
Did you perhaps forget to attach the patch? Either way, the preferred
method for patches/issues is our Jira project at [1]. If you could create
one or more issues over there and attach the patches I will take a look and
see if there are any problems wrt Eclipse etc.
Out of curiosity, you are using XCode? Does it handle C properly? If so, I
think it would be a nice addition to our supported IDE's!
>
> Looking forward to hearing more about the upcoming
> mini-hackathon and where I could potentially focus my
> efforts to best help the community.
>
Do you have any specific area where your interests are? I guess/hope that
the hackathon will focus on Remote Services. Another area which is rather
new, but also interesting, is Native-OSGi and the specification work we
want to start on. See [2] and [3] for some more info.
Thanks for your interest!
[1]: http://issues.apache.org/jira/browse/CELIX
[2]: http://incubator.markmail.org/thread/jbv7ytketpms56hc
[3]: http://blog.cppmicroservices.org/2013/06/14/native-osgi-rfp/
--
Met vriendelijke groet,
Alexander Broekhuis