From: William S F. <ws...@fu...> - 2014-05-24 13:37:18
|
Heads up... I'd like to do a 3.0.1 release in the next couple of days. Is there anything that desperately needs to be put in before I release? In particular, Oliver, are you okay with the Javascript module as is? William |
From: Oliver B. <oli...@go...> - 2014-05-24 18:40:36
|
On Sat, 24 May 2014 15:37:08 +0200, William S Fulton <ws...@fu...> wrote: > Heads up... I'd like to do a 3.0.1 release in the next couple of days. > Is there anything that desperately needs to be put in before I release? > In particular, Oliver, are you okay with the Javascript module as is? > > William Hi William! As a start, I am okay with it. Eric has suggested a bunch of improvements. Also, the travis-osx tries revealed some issues. I am not able to fix all those in the next days. So I would prefer to update the documentation in that regard. Cheers, Oliver |
From: William S F. <ws...@fu...> - 2014-05-24 18:43:46
|
On 24/05/14 19:40, Oliver Buchtala wrote: > On Sat, 24 May 2014 15:37:08 +0200, William S Fulton > <ws...@fu...> wrote: > >> Heads up... I'd like to do a 3.0.1 release in the next couple of days. >> Is there anything that desperately needs to be put in before I release? >> In particular, Oliver, are you okay with the Javascript module as is? >> >> William > > Hi William! > > As a start, I am okay with it. > Eric has suggested a bunch of improvements. Also, the travis-osx tries > revealed some issues. > I am not able to fix all those in the next days. So I would prefer to > update the documentation in that regard. That's fine, osx support can polished off in 3.0.2. I'll look out for your doc changes instead. I don't mind delaying it by a few more days if you would prefer. William |
From: Oliver B. <oli...@go...> - 2014-05-24 18:46:09
|
On Sat, 24 May 2014 20:43:25 +0200, William S Fulton <ws...@fu...> wrote: > On 24/05/14 19:40, Oliver Buchtala wrote: > That's fine, osx support can polished off in 3.0.2. I'll look out for > your doc changes instead. I don't mind delaying it by a few more days if > you would prefer. > You will have it by tomorrow evening at latest. I will ping you. Cheers, Oliver |
From: Oliver B. <oli...@go...> - 2014-05-26 19:40:29
|
Hi William, I added a section about known issues... It would be great to have Eric to have a look over it - as he is currently the most active user of the module (I believe...)... Cheers, Oliver |
From: Eric W. <ewm...@gm...> - 2014-05-26 23:16:07
|
On 5/26/14, Oliver Buchtala <oli...@go...> wrote: > Hi William, > > I added a section about known issues... > It would be great to have Eric to have a look over it - as he is > currently the most active user of the module (I believe...)... > > Cheers, > Oliver I just sent a reply to Oliver from his direct email to me. Thanks, Eric -- Beginning iPhone Games Development http://playcontrol.net/iphonegamebook/ |
From: Oliver B. <oli...@go...> - 2014-05-27 08:49:22
|
On Tue, 27 May 2014 01:16:01 +0200, Eric Wing <ewm...@gm...> wrote: > > I just sent a reply to Oliver from his direct email to me. > Hi William, I have updated the documentation according to Eric's suggestions. This should be it. Cheers, Oliver |
From: William S F. <ws...@fu...> - 2014-05-27 18:00:27
|
On 27/05/14 09:49, Oliver Buchtala wrote: > On Tue, 27 May 2014 01:16:01 +0200, Eric Wing <ewm...@gm...> wrote: > >> >> I just sent a reply to Oliver from his direct email to me. >> > > Hi William, > > I have updated the documentation according to Eric's suggestions. > This should be it. > Great, I'll push the release out tonight. William |
From: William S F. <ws...@fu...> - 2014-05-27 18:45:14
|
On 27/05/14 19:00, William S Fulton wrote: >> I have updated the documentation according to Eric's suggestions. >> This should be it. >> > Great, I'll push the release out tonight. > Oliver, I'll update http://swig.org and include Javascript after the release. What should the exit points on the lhs be for JS? http://nodejs.org: Javascript - node.js http://www.webkit.org: Javascript - Webkit ??? Javascript - v8 Please corect/advise. William |
From: Oliver B. <oli...@go...> - 2014-05-27 18:51:06
|
On Tue, 27 May 2014 20:44:53 +0200, William S Fulton <ws...@fu...> wrote: > I'll update http://swig.org and include Javascript after the release. > What should the exit points on the lhs be for JS? > > http://nodejs.org: Javascript - node.js > http://www.webkit.org: Javascript - Webkit Those are fine. > ??? Javascript - v8 I think this one would be the best: https://developers.google.com/v8/ Cheers, Oliver |
From: William S F. <ws...@fu...> - 2014-05-27 19:15:57
|
On 27/05/14 19:50, Oliver Buchtala wrote: > On Tue, 27 May 2014 20:44:53 +0200, William S Fulton > <ws...@fu...> wrote: > >> I'll update http://swig.org and include Javascript after the release. >> What should the exit points on the lhs be for JS? >> >> http://nodejs.org: Javascript - node.js >> http://www.webkit.org: Javascript - Webkit > > Those are fine. > >> ??? Javascript - v8 > I think this one would be the best: https://developers.google.com/v8/ > Thanks, perhaps add this to Javascript.html too? William |
From: Oliver B. <oli...@go...> - 2014-05-27 19:38:33
|
On Tue, 27 May 2014 21:15:45 +0200, William S Fulton <ws...@fu...> wrote: > Thanks, perhaps add this to Javascript.html too? Done. Oliver |
From: Karl W. <kar...@gm...> - 2014-05-24 19:42:07
|
Just to round out the out-of-source-tree changes, I've now pushed a patch to remove the generated example Makefiles by searching for the corresponding source Makefile, as you suggested. I also modified the Travis build to print out any files that get left over after running maintainer-clean, so you can see whether everything is being removed. Cheers, Karl On 24 May 2014 15:37, William S Fulton <ws...@fu...> wrote: > Heads up... I'd like to do a 3.0.1 release in the next couple of days. > Is there anything that desperately needs to be put in before I release? > In particular, Oliver, are you okay with the Javascript module as is? > > William > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Swig-devel mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-devel |
From: William S F. <ws...@fu...> - 2014-05-28 17:33:20
|
Thanks. How about failing the Travis build if there are any files left after printing them out? I think it would also be a bit better if this was all in the makefile, so perhaps a check-maintainer-clean target? I can also then invoke the target from the openSUSE Build Service testing environment, which is doing in source builds and testing in contrast to out of source builds on Travis. William On 24/05/14 20:41, Karl Wette wrote: > Just to round out the out-of-source-tree changes, I've now pushed a > patch to remove the generated example Makefiles by searching for the > corresponding source Makefile, as you suggested. I also modified the > Travis build to print out any files that get left over after running > maintainer-clean, so you can see whether everything is being removed. > > Cheers, Karl > > On 24 May 2014 15:37, William S Fulton <ws...@fu...> wrote: >> Heads up... I'd like to do a 3.0.1 release in the next couple of days. >> Is there anything that desperately needs to be put in before I release? >> In particular, Oliver, are you okay with the Javascript module as is? >> >> William >> >> ------------------------------------------------------------------------------ >> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE >> Instantly run your Selenium tests across 300+ browser/OS combos. >> Get unparalleled scalability from the best Selenium testing platform available >> Simple to use. Nothing to install. Get started now for free." >> http://p.sf.net/sfu/SauceLabs >> _______________________________________________ >> Swig-devel mailing list >> Swi...@li... >> https://lists.sourceforge.net/lists/listinfo/swig-devel > |
From: Karl W. <kar...@gm...> - 2014-05-29 00:46:09
|
Done - there's now a check-maintainer-clean target, run by the Travis build, which will fail if any files are missed by maintainer-clean. However this will only work for out-of-source builds, since for in-source builds you can't generally tell source files from left-over build products. The Travis-built languages should all now properly clean up when maintainer-clean is run. Cheers, Karl On 28 May 2014 19:33, William S Fulton <ws...@fu...> wrote: > Thanks. How about failing the Travis build if there are any files left after > printing them out? I think it would also be a bit better if this was all in > the makefile, so perhaps a check-maintainer-clean target? I can also then > invoke the target from the openSUSE Build Service testing environment, which > is doing in source builds and testing in contrast to out of source builds on > Travis. > > William > > > On 24/05/14 20:41, Karl Wette wrote: >> >> Just to round out the out-of-source-tree changes, I've now pushed a >> patch to remove the generated example Makefiles by searching for the >> corresponding source Makefile, as you suggested. I also modified the >> Travis build to print out any files that get left over after running >> maintainer-clean, so you can see whether everything is being removed. >> >> Cheers, Karl >> >> On 24 May 2014 15:37, William S Fulton <ws...@fu...> wrote: >>> >>> Heads up... I'd like to do a 3.0.1 release in the next couple of days. >>> Is there anything that desperately needs to be put in before I release? >>> In particular, Oliver, are you okay with the Javascript module as is? >>> >>> William >>> >>> >>> ------------------------------------------------------------------------------ >>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE >>> Instantly run your Selenium tests across 300+ browser/OS combos. >>> Get unparalleled scalability from the best Selenium testing platform >>> available >>> Simple to use. Nothing to install. Get started now for free." >>> http://p.sf.net/sfu/SauceLabs >>> _______________________________________________ >>> Swig-devel mailing list >>> Swi...@li... >>> https://lists.sourceforge.net/lists/listinfo/swig-devel >> >> > |
From: Karl W. <kar...@gm...> - 2014-05-29 14:02:49
|
Just noticed a bug in one of my previous commits - the Python cleanup was deleting the original _runme.py scripts from the source directory when doing in-source-tree builds. I've just pushed a fix. Cheers, Karl On 29 May 2014 02:45, Karl Wette <kar...@gm...> wrote: > Done - there's now a check-maintainer-clean target, run by the Travis > build, which will fail if any files are missed by maintainer-clean. > However this will only work for out-of-source builds, since for > in-source builds you can't generally tell source files from left-over > build products. The Travis-built languages should all now properly > clean up when maintainer-clean is run. > > Cheers, Karl > > On 28 May 2014 19:33, William S Fulton <ws...@fu...> wrote: >> Thanks. How about failing the Travis build if there are any files left after >> printing them out? I think it would also be a bit better if this was all in >> the makefile, so perhaps a check-maintainer-clean target? I can also then >> invoke the target from the openSUSE Build Service testing environment, which >> is doing in source builds and testing in contrast to out of source builds on >> Travis. >> >> William >> >> >> On 24/05/14 20:41, Karl Wette wrote: >>> >>> Just to round out the out-of-source-tree changes, I've now pushed a >>> patch to remove the generated example Makefiles by searching for the >>> corresponding source Makefile, as you suggested. I also modified the >>> Travis build to print out any files that get left over after running >>> maintainer-clean, so you can see whether everything is being removed. >>> >>> Cheers, Karl >>> >>> On 24 May 2014 15:37, William S Fulton <ws...@fu...> wrote: >>>> >>>> Heads up... I'd like to do a 3.0.1 release in the next couple of days. >>>> Is there anything that desperately needs to be put in before I release? >>>> In particular, Oliver, are you okay with the Javascript module as is? >>>> >>>> William >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE >>>> Instantly run your Selenium tests across 300+ browser/OS combos. >>>> Get unparalleled scalability from the best Selenium testing platform >>>> available >>>> Simple to use. Nothing to install. Get started now for free." >>>> http://p.sf.net/sfu/SauceLabs >>>> _______________________________________________ >>>> Swig-devel mailing list >>>> Swi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/swig-devel >>> >>> >> |
From: William S F. <ws...@fu...> - 2014-06-02 06:39:59
|
Thanks for all the clean improvements. Unfortunately you ended up fixing a whole lot more clean problems than I thought there'd be. Adding the check-maintainer-clean to Travis builds will help keep it in a good state going forwards, so this is all good stuff. William On 29/05/14 15:02, Karl Wette wrote: > Just noticed a bug in one of my previous commits - the Python cleanup > was deleting the original _runme.py scripts from the source directory > when doing in-source-tree builds. I've just pushed a fix. > > Cheers, Karl > > On 29 May 2014 02:45, Karl Wette <kar...@gm...> wrote: >> Done - there's now a check-maintainer-clean target, run by the Travis >> build, which will fail if any files are missed by maintainer-clean. >> However this will only work for out-of-source builds, since for >> in-source builds you can't generally tell source files from left-over >> build products. The Travis-built languages should all now properly >> clean up when maintainer-clean is run. >> >> Cheers, Karl >> >> On 28 May 2014 19:33, William S Fulton <ws...@fu...> wrote: >>> Thanks. How about failing the Travis build if there are any files left after >>> printing them out? I think it would also be a bit better if this was all in >>> the makefile, so perhaps a check-maintainer-clean target? I can also then >>> invoke the target from the openSUSE Build Service testing environment, which >>> is doing in source builds and testing in contrast to out of source builds on >>> Travis. >>> >>> William >>> >>> >>> On 24/05/14 20:41, Karl Wette wrote: >>>> >>>> Just to round out the out-of-source-tree changes, I've now pushed a >>>> patch to remove the generated example Makefiles by searching for the >>>> corresponding source Makefile, as you suggested. I also modified the >>>> Travis build to print out any files that get left over after running >>>> maintainer-clean, so you can see whether everything is being removed. >>>> >>>> Cheers, Karl >>>> >>>> On 24 May 2014 15:37, William S Fulton <ws...@fu...> wrote: >>>>> >>>>> Heads up... I'd like to do a 3.0.1 release in the next couple of days. >>>>> Is there anything that desperately needs to be put in before I release? >>>>> In particular, Oliver, are you okay with the Javascript module as is? >>>>> >>>>> William >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE >>>>> Instantly run your Selenium tests across 300+ browser/OS combos. >>>>> Get unparalleled scalability from the best Selenium testing platform >>>>> available >>>>> Simple to use. Nothing to install. Get started now for free." >>>>> http://p.sf.net/sfu/SauceLabs >>>>> _______________________________________________ >>>>> Swig-devel mailing list >>>>> Swi...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/swig-devel >>>> >>>> >>> > |