An organization can be created on github, and the official repository can be kept at <a href="http://github.com/organizationname/chuck">github.com/organizationname/chuck</a>.<div><br></div><div>Unfortunately the "ChucK" name is taken, so the organization cannot be called this.</div>
<div><br></div><div>I would be happy to start a "CCRMA" organization on github, I've been meaning to make this suggestion to others at CCRMA who are working on joint projects. However, I think it is important to hear from Ge, Spencer, et. al. on if they want chuck to be mirrored at <a href="http://github.com/ccrma/chuck">github.com/ccrma/chuck</a> or not.<br clear="all">
----------<div>Colin Sullivan<br></div><br>
<br><br><div class="gmail_quote">On Fri, Feb 3, 2012 at 7:08 AM, mike clemow <span dir="ltr"><<a href="mailto:michaelclemow@gmail.com">michaelclemow@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, I made this change at one point:<div><br></div><div><a href="https://github.com/clembie/mc_chuck_dev" target="_blank">https://github.com/clembie/mc_chuck_dev</a></div><div><br></div><div>Which was really a trivial little change involving a stubbed out but unpopulated method in Object that allowed for a very powerful operation when making generic handlers for things like UGens and other objects (see example in README). If I started mucking around with this stuff again, I'd definitely prefer to fork from a git repo rather than CVS. </div>
<div><br></div><div>I've always wanted to be able to ask an object for the name of its super class, for instance.</div><div><br></div><div>It would be really nice to get some documentation on the current implementation of ChucK in order to facilitate this kind of community experimentation.</div>
<div><br></div><div>Just dreaming here...</div><div><br></div><div><div class="im">//mike<br clear="all"><div><br></div><a href="http://michaelclemow.com" target="_blank">http://michaelclemow.com</a><br><a href="http://semiotech.org" target="_blank">http://semiotech.org</a><br>
<br><br>
<br><br></div><div><div class="h5"><div class="gmail_quote">On Fri, Feb 3, 2012 at 9:55 AM, Remi Gillig <span dir="ltr"><<a href="mailto:remigillig@gmail.com" target="_blank">remigillig@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is truly great to see that many people interested ! I agree that<br>
my own changes should not be in the main trunk but this is how I would<br>
have done it if I forked the main chuck github project if there was<br>
one. After that I could have made a pull request for my changes if the<br>
original repository maintainers wanted to integrate my changes.<br>
<br>
Anyway, this is all conditional and I would like some input from the<br>
current SVN committers (Spencer Salazar and Ge Wang) if they could be<br>
ready to make this change. Nowadays, all platforms supported by ChucK<br>
have decent Git support and using Git in combination with GitHub<br>
really can make wonders to an open source project like ChucK.<br>
<br>
I hope this message will reach them. In the meantime, I will try to<br>
keep my github in sync with the SVN one but I can't guarantee<br>
anything.<br>
<br>
As for contribution, if anyone is up for it, the current<br>
CMakeLists.txt file only supports Windows (because I don't have<br>
anything else setup) so it needs Linux and MacOSX support (at least<br>
with default options). And maybe later add support for compilation<br>
options (such as choose for HID support or not etc.).<br>
<br>
Again, thanks for the feedback !<br>
<br>
Cheers,<br>
Remi Gillig.<br>
<br>
On 3 February 2012 15:29, <<a href="mailto:chuck-dev-request@lists.cs.princeton.edu" target="_blank">chuck-dev-request@lists.cs.princeton.edu</a>> wrote:<br>
> Send chuck-dev mailing list submissions to<br>
> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:chuck-dev-request@lists.cs.princeton.edu" target="_blank">chuck-dev-request@lists.cs.princeton.edu</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:chuck-dev-owner@lists.cs.princeton.edu" target="_blank">chuck-dev-owner@lists.cs.princeton.edu</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of chuck-dev digest..."<br>
><br>
> Today's Topics:<br>
><br>
> 1. ChucK GitHub (Remi Gillig)<br>
> 2. Re: ChucK GitHub (Colin Sullivan)<br>
> 3. Re: ChucK GitHub (Stephen Sinclair)<br>
> 4. Re: ChucK GitHub (Ricardo Fabbri)<br>
> 5. Re: ChucK GitHub (mike clemow)<br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: Remi Gillig <<a href="mailto:remigillig@gmail.com" target="_blank">remigillig@gmail.com</a>><br>
> To: <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
> Cc:<br>
> Date: Fri, 3 Feb 2012 00:50:54 +0100<br>
> Subject: [chuck-dev] ChucK GitHub<br>
> Hello all,<br>
><br>
> It's not that I don't like SVN but there are cool alternatives for<br>
> open source projects now. So I put ChucK on GitHub, I dream that you<br>
> would adopt this for future commits. The biggest advantage is the<br>
> "fork + pull" mechanic where someone can fork a project, do some<br>
> fixes, modifications, additions etc. and you can pull his changes into<br>
> the original repository. I know changing SCM is a big change in a<br>
> project but I had to go the mailing list archives to find the SVN URL<br>
> and I would love to see more contributions to ChucK.<br>
><br>
> Also a big change in many projects, is the change for the build<br>
> system. For Windows, the platform I'm originally interested in, I saw<br>
> that there were Visual 6 projects which is quite outdated. For the<br>
> benefit of everyone, I made a preliminary CMake build file which can<br>
> right now build ChucK on Visual Studio 2010 for example. CMake is a<br>
> bit like make but can generate projects for a number of platforms.<br>
><br>
> So, to summarize, I imported the SVN repository (revision 93) into<br>
> GitHub at this address : <a href="https://github.com/speps/chuck" target="_blank">https://github.com/speps/chuck</a><br>
> My changes are already there, some minor fixes so that it builds on<br>
> Windows (without HID, DirectInput support was outdated, without OTF<br>
> server too. I did not want to be asked about Windows firewall for<br>
> ChucK). These options should be CMake options if anyone is up for it.<br>
><br>
> Anyway, I hope to hear from the developers community about a possible<br>
> switch over to GitHub which would be great for ChucK (I had to go the<br>
> mailing lists to realize that the latest version from the home page<br>
> dates from around 2009).<br>
><br>
> Cheers,<br>
> Remi Gillig.<br>
><br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: Colin Sullivan <<a href="mailto:colinsul@gmail.com" target="_blank">colinsul@gmail.com</a>><br>
> To: ChucK Developer Mailing List <<a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a>><br>
> Cc:<br>
> Date: Thu, 2 Feb 2012 18:24:16 -0800<br>
> Subject: Re: [chuck-dev] ChucK GitHub<br>
> I am in support of this idea, but I think it may be a better idea to keep the "master" branch representative of the official ChucK "trunk", and keep any other commits in other branches until they are merged into ChucK "officially".<br>
><br>
> Just my two cents.<br>
> ----------<br>
> Colin Sullivan<br>
><br>
><br>
><br>
> On Thu, Feb 2, 2012 at 3:50 PM, Remi Gillig <<a href="mailto:remigillig@gmail.com" target="_blank">remigillig@gmail.com</a>> wrote:<br>
>><br>
>> Hello all,<br>
>><br>
>> It's not that I don't like SVN but there are cool alternatives for<br>
>> open source projects now. So I put ChucK on GitHub, I dream that you<br>
>> would adopt this for future commits. The biggest advantage is the<br>
>> "fork + pull" mechanic where someone can fork a project, do some<br>
>> fixes, modifications, additions etc. and you can pull his changes into<br>
>> the original repository. I know changing SCM is a big change in a<br>
>> project but I had to go the mailing list archives to find the SVN URL<br>
>> and I would love to see more contributions to ChucK.<br>
>><br>
>> Also a big change in many projects, is the change for the build<br>
>> system. For Windows, the platform I'm originally interested in, I saw<br>
>> that there were Visual 6 projects which is quite outdated. For the<br>
>> benefit of everyone, I made a preliminary CMake build file which can<br>
>> right now build ChucK on Visual Studio 2010 for example. CMake is a<br>
>> bit like make but can generate projects for a number of platforms.<br>
>><br>
>> So, to summarize, I imported the SVN repository (revision 93) into<br>
>> GitHub at this address : <a href="https://github.com/speps/chuck" target="_blank">https://github.com/speps/chuck</a><br>
>> My changes are already there, some minor fixes so that it builds on<br>
>> Windows (without HID, DirectInput support was outdated, without OTF<br>
>> server too. I did not want to be asked about Windows firewall for<br>
>> ChucK). These options should be CMake options if anyone is up for it.<br>
>><br>
>> Anyway, I hope to hear from the developers community about a possible<br>
>> switch over to GitHub which would be great for ChucK (I had to go the<br>
>> mailing lists to realize that the latest version from the home page<br>
>> dates from around 2009).<br>
>><br>
>> Cheers,<br>
>> Remi Gillig.<br>
>> _______________________________________________<br>
>> chuck-dev mailing list<br>
>> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
><br>
><br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: Stephen Sinclair <<a href="mailto:radarsat1@gmail.com" target="_blank">radarsat1@gmail.com</a>><br>
> To: ChucK Developer Mailing List <<a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a>><br>
> Cc:<br>
> Date: Thu, 2 Feb 2012 22:32:21 -0500<br>
> Subject: Re: [chuck-dev] ChucK GitHub<br>
> I had tried doing that quite a long time ago ;)<br>
><br>
> <a href="http://repo.or.cz/w/chuck-blob.git" target="_blank">http://repo.or.cz/w/chuck-blob.git</a><br>
><br>
> But lost interest in keeping it up to date.. I hope you have more<br>
> luck! Personally I think the project would benefit greatly by moving<br>
> completely to git.<br>
><br>
> Steve<br>
><br>
> On Thu, Feb 2, 2012 at 9:24 PM, Colin Sullivan <<a href="mailto:colinsul@gmail.com" target="_blank">colinsul@gmail.com</a>> wrote:<br>
>> I am in support of this idea, but I think it may be a better idea to keep<br>
>> the "master" branch representative of the official ChucK "trunk", and keep<br>
>> any other commits in other branches until they are merged into ChucK<br>
>> "officially".<br>
>><br>
>> Just my two cents.<br>
>> ----------<br>
>> Colin Sullivan<br>
>><br>
>><br>
>><br>
>> On Thu, Feb 2, 2012 at 3:50 PM, Remi Gillig <<a href="mailto:remigillig@gmail.com" target="_blank">remigillig@gmail.com</a>> wrote:<br>
>>><br>
>>> Hello all,<br>
>>><br>
>>> It's not that I don't like SVN but there are cool alternatives for<br>
>>> open source projects now. So I put ChucK on GitHub, I dream that you<br>
>>> would adopt this for future commits. The biggest advantage is the<br>
>>> "fork + pull" mechanic where someone can fork a project, do some<br>
>>> fixes, modifications, additions etc. and you can pull his changes into<br>
>>> the original repository. I know changing SCM is a big change in a<br>
>>> project but I had to go the mailing list archives to find the SVN URL<br>
>>> and I would love to see more contributions to ChucK.<br>
>>><br>
>>> Also a big change in many projects, is the change for the build<br>
>>> system. For Windows, the platform I'm originally interested in, I saw<br>
>>> that there were Visual 6 projects which is quite outdated. For the<br>
>>> benefit of everyone, I made a preliminary CMake build file which can<br>
>>> right now build ChucK on Visual Studio 2010 for example. CMake is a<br>
>>> bit like make but can generate projects for a number of platforms.<br>
>>><br>
>>> So, to summarize, I imported the SVN repository (revision 93) into<br>
>>> GitHub at this address : <a href="https://github.com/speps/chuck" target="_blank">https://github.com/speps/chuck</a><br>
>>> My changes are already there, some minor fixes so that it builds on<br>
>>> Windows (without HID, DirectInput support was outdated, without OTF<br>
>>> server too. I did not want to be asked about Windows firewall for<br>
>>> ChucK). These options should be CMake options if anyone is up for it.<br>
>>><br>
>>> Anyway, I hope to hear from the developers community about a possible<br>
>>> switch over to GitHub which would be great for ChucK (I had to go the<br>
>>> mailing lists to realize that the latest version from the home page<br>
>>> dates from around 2009).<br>
>>><br>
>>> Cheers,<br>
>>> Remi Gillig.<br>
>>> _______________________________________________<br>
>>> chuck-dev mailing list<br>
>>> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> chuck-dev mailing list<br>
>> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
>><br>
><br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: Ricardo Fabbri <<a href="mailto:rfabbri@gmail.com" target="_blank">rfabbri@gmail.com</a>><br>
> To: ChucK Developer Mailing List <<a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a>><br>
> Cc:<br>
> Date: Fri, 3 Feb 2012 01:42:13 -0200<br>
> Subject: Re: [chuck-dev] ChucK GitHub<br>
> +1 to Git.<br>
><br>
> Ricardo Fabbri<br>
> --<br>
> Linux registered user #175401<br>
> <a href="http://www.lems.brown.edu/~rfabbri" target="_blank">www.lems.brown.edu/~rfabbri</a><br>
> <a href="http://pt.wikipedia.org/wiki/IPRJ" target="_blank">pt.wikipedia.org/wiki/IPRJ</a><br>
> <a href="http://labmacambira.sf.net" target="_blank">labmacambira.sf.net</a><br>
><br>
><br>
><br>
> On Fri, Feb 3, 2012 at 1:32 AM, Stephen Sinclair <<a href="mailto:radarsat1@gmail.com" target="_blank">radarsat1@gmail.com</a>> wrote:<br>
>> I had tried doing that quite a long time ago ;)<br>
>><br>
>> <a href="http://repo.or.cz/w/chuck-blob.git" target="_blank">http://repo.or.cz/w/chuck-blob.git</a><br>
>><br>
>> But lost interest in keeping it up to date.. I hope you have more<br>
>> luck! Personally I think the project would benefit greatly by moving<br>
>> completely to git.<br>
>><br>
>> Steve<br>
>><br>
>> On Thu, Feb 2, 2012 at 9:24 PM, Colin Sullivan <<a href="mailto:colinsul@gmail.com" target="_blank">colinsul@gmail.com</a>> wrote:<br>
>>> I am in support of this idea, but I think it may be a better idea to keep<br>
>>> the "master" branch representative of the official ChucK "trunk", and keep<br>
>>> any other commits in other branches until they are merged into ChucK<br>
>>> "officially".<br>
>>><br>
>>> Just my two cents.<br>
>>> ----------<br>
>>> Colin Sullivan<br>
>>><br>
>>><br>
>>><br>
>>> On Thu, Feb 2, 2012 at 3:50 PM, Remi Gillig <<a href="mailto:remigillig@gmail.com" target="_blank">remigillig@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Hello all,<br>
>>>><br>
>>>> It's not that I don't like SVN but there are cool alternatives for<br>
>>>> open source projects now. So I put ChucK on GitHub, I dream that you<br>
>>>> would adopt this for future commits. The biggest advantage is the<br>
>>>> "fork + pull" mechanic where someone can fork a project, do some<br>
>>>> fixes, modifications, additions etc. and you can pull his changes into<br>
>>>> the original repository. I know changing SCM is a big change in a<br>
>>>> project but I had to go the mailing list archives to find the SVN URL<br>
>>>> and I would love to see more contributions to ChucK.<br>
>>>><br>
>>>> Also a big change in many projects, is the change for the build<br>
>>>> system. For Windows, the platform I'm originally interested in, I saw<br>
>>>> that there were Visual 6 projects which is quite outdated. For the<br>
>>>> benefit of everyone, I made a preliminary CMake build file which can<br>
>>>> right now build ChucK on Visual Studio 2010 for example. CMake is a<br>
>>>> bit like make but can generate projects for a number of platforms.<br>
>>>><br>
>>>> So, to summarize, I imported the SVN repository (revision 93) into<br>
>>>> GitHub at this address : <a href="https://github.com/speps/chuck" target="_blank">https://github.com/speps/chuck</a><br>
>>>> My changes are already there, some minor fixes so that it builds on<br>
>>>> Windows (without HID, DirectInput support was outdated, without OTF<br>
>>>> server too. I did not want to be asked about Windows firewall for<br>
>>>> ChucK). These options should be CMake options if anyone is up for it.<br>
>>>><br>
>>>> Anyway, I hope to hear from the developers community about a possible<br>
>>>> switch over to GitHub which would be great for ChucK (I had to go the<br>
>>>> mailing lists to realize that the latest version from the home page<br>
>>>> dates from around 2009).<br>
>>>><br>
>>>> Cheers,<br>
>>>> Remi Gillig.<br>
>>>> _______________________________________________<br>
>>>> chuck-dev mailing list<br>
>>>> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>>>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> chuck-dev mailing list<br>
>>> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
>>><br>
>> _______________________________________________<br>
>> chuck-dev mailing list<br>
>> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
><br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: mike clemow <<a href="mailto:michaelclemow@gmail.com" target="_blank">michaelclemow@gmail.com</a>><br>
> To: ChucK Developer Mailing List <<a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a>><br>
> Cc:<br>
> Date: Fri, 3 Feb 2012 09:29:17 -0500<br>
> Subject: Re: [chuck-dev] ChucK GitHub<br>
> I'll throw my hat in the ring for for git.<br>
><br>
> I'm wondering how many users have personal changes to the main ChucK branch... I've dabbled in this realm before, but I'm curious what other changes people have made.<br>
><br>
> //mike<br>
><br>
> <a href="http://michaelclemow.com" target="_blank">http://michaelclemow.com</a><br>
> <a href="http://semiotech.org" target="_blank">http://semiotech.org</a><br>
><br>
><br>
><br>
><br>
> On Thu, Feb 2, 2012 at 10:42 PM, Ricardo Fabbri <<a href="mailto:rfabbri@gmail.com" target="_blank">rfabbri@gmail.com</a>> wrote:<br>
>><br>
>> +1 to Git.<br>
>><br>
>> Ricardo Fabbri<br>
>> --<br>
>> Linux registered user #175401<br>
>> <a href="http://www.lems.brown.edu/~rfabbri" target="_blank">www.lems.brown.edu/~rfabbri</a><br>
>> <a href="http://pt.wikipedia.org/wiki/IPRJ" target="_blank">pt.wikipedia.org/wiki/IPRJ</a><br>
>> <a href="http://labmacambira.sf.net" target="_blank">labmacambira.sf.net</a><br>
>><br>
>><br>
>><br>
>> On Fri, Feb 3, 2012 at 1:32 AM, Stephen Sinclair <<a href="mailto:radarsat1@gmail.com" target="_blank">radarsat1@gmail.com</a>> wrote:<br>
>> > I had tried doing that quite a long time ago ;)<br>
>> ><br>
>> > <a href="http://repo.or.cz/w/chuck-blob.git" target="_blank">http://repo.or.cz/w/chuck-blob.git</a><br>
>> ><br>
>> > But lost interest in keeping it up to date.. I hope you have more<br>
>> > luck! Personally I think the project would benefit greatly by moving<br>
>> > completely to git.<br>
>> ><br>
>> > Steve<br>
>> ><br>
>> > On Thu, Feb 2, 2012 at 9:24 PM, Colin Sullivan <<a href="mailto:colinsul@gmail.com" target="_blank">colinsul@gmail.com</a>> wrote:<br>
>> >> I am in support of this idea, but I think it may be a better idea to keep<br>
>> >> the "master" branch representative of the official ChucK "trunk", and keep<br>
>> >> any other commits in other branches until they are merged into ChucK<br>
>> >> "officially".<br>
>> >><br>
>> >> Just my two cents.<br>
>> >> ----------<br>
>> >> Colin Sullivan<br>
>> >><br>
>> >><br>
>> >><br>
>> >> On Thu, Feb 2, 2012 at 3:50 PM, Remi Gillig <<a href="mailto:remigillig@gmail.com" target="_blank">remigillig@gmail.com</a>> wrote:<br>
>> >>><br>
>> >>> Hello all,<br>
>> >>><br>
>> >>> It's not that I don't like SVN but there are cool alternatives for<br>
>> >>> open source projects now. So I put ChucK on GitHub, I dream that you<br>
>> >>> would adopt this for future commits. The biggest advantage is the<br>
>> >>> "fork + pull" mechanic where someone can fork a project, do some<br>
>> >>> fixes, modifications, additions etc. and you can pull his changes into<br>
>> >>> the original repository. I know changing SCM is a big change in a<br>
>> >>> project but I had to go the mailing list archives to find the SVN URL<br>
>> >>> and I would love to see more contributions to ChucK.<br>
>> >>><br>
>> >>> Also a big change in many projects, is the change for the build<br>
>> >>> system. For Windows, the platform I'm originally interested in, I saw<br>
>> >>> that there were Visual 6 projects which is quite outdated. For the<br>
>> >>> benefit of everyone, I made a preliminary CMake build file which can<br>
>> >>> right now build ChucK on Visual Studio 2010 for example. CMake is a<br>
>> >>> bit like make but can generate projects for a number of platforms.<br>
>> >>><br>
>> >>> So, to summarize, I imported the SVN repository (revision 93) into<br>
>> >>> GitHub at this address : <a href="https://github.com/speps/chuck" target="_blank">https://github.com/speps/chuck</a><br>
>> >>> My changes are already there, some minor fixes so that it builds on<br>
>> >>> Windows (without HID, DirectInput support was outdated, without OTF<br>
>> >>> server too. I did not want to be asked about Windows firewall for<br>
>> >>> ChucK). These options should be CMake options if anyone is up for it.<br>
>> >>><br>
>> >>> Anyway, I hope to hear from the developers community about a possible<br>
>> >>> switch over to GitHub which would be great for ChucK (I had to go the<br>
>> >>> mailing lists to realize that the latest version from the home page<br>
>> >>> dates from around 2009).<br>
>> >>><br>
>> >>> Cheers,<br>
>> >>> Remi Gillig.<br>
>> >>> _______________________________________________<br>
>> >>> chuck-dev mailing list<br>
>> >>> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>> >>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> chuck-dev mailing list<br>
>> >> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>> >> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
>> >><br>
>> > _______________________________________________<br>
>> > chuck-dev mailing list<br>
>> > <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>> > <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
>> _______________________________________________<br>
>> chuck-dev mailing list<br>
>> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> chuck-dev mailing list<br>
> <a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
><br>
_______________________________________________<br>
chuck-dev mailing list<br>
<a href="mailto:chuck-dev@lists.cs.princeton.edu" target="_blank">chuck-dev@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
chuck-dev mailing list<br>
<a href="mailto:chuck-dev@lists.cs.princeton.edu">chuck-dev@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
<br></blockquote></div><br></div>