From my Android phone on T-Mobile. The first nationwide 4G network.
-------- Original message --------
From: Oleg Kolosov <[email protected]>
Date: 02/10/2014 3:09 PM (GMT-07:00)
To: Matt Welland <[email protected]>,chicken-users <[email protected]>
Subject: Re: [Chicken-users] CMake build support
On 02/11/14 01:07, Matt Welland wrote:
Hi Oleg,
What is the purpose of switching to cmake? Can the transition be done without
adding another dependency to building for mingw-msys?
I guess my concern is that even if cmake is an improvement over make that the
impact can still be negative on the community.
For me the interesting platforms for chicken are:
Linux (several generations in current use).
Android (admittedly this is in my dreams :))
Windows mingw-msys
When you are done can I expect that my builds for these platforms will be as
easy as they are today?
I missed the discussion of this on the chicken lists so my appologies if this
has been hashed to death but in my opinion open source projects are very
vunerable to pertubations and I really want to see chicken thriving, not just
surviving. A change like this alienating even a single strong developer can
hurt. Hopefully the developers are already on board with your vision in
this.
> Hi!
> There was not any discussion, I've decided to
> try first, discuss later. Consider this thread the
> initial request for comments.
Ah! Ok, fair enough.
> I maintain build system for projects at
> my workplace, we are cross-compiling
> for embedded platform, desktop, there
> are plans for mobile, and dealing with
> Chicken (with eggs and dependencies)
> as projects grow becomes really painful.
> So this is partially internal, and partially
> personal project. I'm trying to implement
> CMake based scripts alongside
> current system. Ideally, it should be
> completely optional.
Ok, I understand. This would certainly ease any transition.
> Current goals are: fix few annoyances
> in building cross Chicken with eggs, a way
> to generate configurable self-contained
> executables, native Windows build (with
> installer). All this might take a long time.
If I read this correctly it sounds as if with CMake it would be possible to
leverage the build system to not merely build chicken but also to install
dependent eggs and even further to use it for the build for the final
application. Is this what you envision?
If so, this is a new idea to me. I see installing chicken as a pre-developmment
step. My application then has it's own makefile 100% independent of chicken.
If CMake resulted in an easier to use deploy mechanism I'd be thrilled. Deploy
is a super cool feature but I seem to have a hard time getting it to work
sometimes.
Matt
--
Regards, Oleg_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users
