Very cool. I'll let headius know we are past that hurdle. Thanks everybody!
On Mon, Mar 1, 2010 at 09:23, Daniel Spiewak wrote:
> Just give it a shot with your stuff. Run a `build` (compile + test) and
> then try to open a shell (preferably JIRB or Scala). If both of those
> work,
> then we ca
Just give it a shot with your stuff. Run a `build` (compile + test) and
then try to open a shell (preferably JIRB or Scala). If both of those work,
then we can have fairly high confidence that things are sorted.
Daniel
On Mon, Mar 1, 2010 at 11:21 AM, Pepijn Van Eeckhoudt <
pepijn.vaneeckho...@
Any ideas on how to test this thoroughly? I can't imagine this causing a
regression as the debugger now shows system is being loaded from msvcrt
which is exactly the method you want to load.
Pepijn
On 1/3/2010 18:17, Daniel Spiewak wrote:
Fix committed in r917597. Note that this only applies
Fix committed in r917597. Note that this only applies when
Buildr::Util::win_os? is true.
Daniel
On Mon, Mar 1, 2010 at 11:13 AM, Pepijn Van Eeckhoudt <
pepijn.vaneeckho...@luciad.com> wrote:
> Or better yet just use LIBC directly instead :)
> So ffi_lib FFI::Platform::LIBC
>
> I'll add this as
Or better yet just use LIBC directly instead :)
So ffi_lib FFI::Platform::LIBC
I'll add this as a comment to BUILDR-348
Pepijn
On 1/3/2010 18:05, Pepijn Van Eeckhoudt wrote:
Aha, that confirms what I suspected. I was about to check the JRuby
source code, so thanks for saving me some digging :)
Aha, that confirms what I suspected. I was about to check the JRuby
source code, so thanks for saving me some digging :)
Adding
ffi_lib "c"
before the attach_function does the trick. map_library_name maps this to
Platform::LIBC and then the attach works correctly.
Pepijn
On 1/3/2010 17:50, A
See my comment on BUILDR-348.
On Mon, Mar 1, 2010 at 08:49, Pepijn Van Eeckhoudt <
pepijn.vaneeckho...@luciad.com> wrote:
> Just tested that; nothing happens. I don't see the vim output and jirb is
> no longer responding to input.
>
> Pepijn
>
>
> On 1/3/2010 17:37, Alex Boisvert wrote:
>
>> They
Just tested that; nothing happens. I don't see the vim output and jirb
is no longer responding to input.
Pepijn
On 1/3/2010 17:37, Alex Boisvert wrote:
They may have fixed system() such that using FFI directly wouldn't be
necessary anymore. A simple test such as "system 'vim'" from jirb on
Wi
They may have fixed system() such that using FFI directly wouldn't be
necessary anymore. A simple test such as "system 'vim'" from jirb on
Windows would confirm.
alex
On Mon, Mar 1, 2010 at 8:16 AM, Antoine Toulme wrote:
> I can contact the jruby folks and see if a jruby update would help - JFF
I can contact the jruby folks and see if a jruby update would help - JFFI is
now 1.0 btw, while it was 0.4 in 1.4.0.
On Mon, Mar 1, 2010 at 08:12, Alex Boisvert wrote:
> On Mon, Mar 1, 2010 at 3:00 AM, Pepijn Van Eeckhoudt <
> pepijn.vaneeckho...@luciad.com> wrote:
>
> > It would be nice if BUIL
On Mon, Mar 1, 2010 at 3:00 AM, Pepijn Van Eeckhoudt <
pepijn.vaneeckho...@luciad.com> wrote:
> It would be nice if BUILDR-348 could be resolved for 1.4.0. We are planning
> on using buildr as internally running on jruby 1.4. Right now this issue
> means I will either have to maintain a custom bui
l on that
since December) and deal with some updates/changes on the release side
(gemcutter).
How does that sound? Are we ready to call the next release 1.4.0?
alex
--
Pepijn Van Eeckhoudt - Project Leader
T +32 16 23 95 91
F +32 16 29 34 22 | pepijn.vaneeckho...@luciad.com
LUCIAD - h
Push complete in r917127. Incidentally, it looks like I do have some
rudimentary specs (which don't seem to be passing, sorry about that). Even
better, it looks like I also took the time to document things, so we can
scratch that off our TODO list.
Daniel
On Sat, Feb 27, 2010 at 10:25 PM, Danie
> @Continuous compilation:
> wow, great ! Can you file bugs around ? That would help me help you.
>
We could, but since the code only exists in my Git fork, there doesn't seem
to be much point at present. :-)
I'll push what I have into the SVN at the soonest possible moment (hopefully
tonight).
n into issues myself running it
> on
> > multi-project buildfile. I have a patch in a git branch somewhere...
> >
> > alex
> >
> > On Sat, Feb 27, 2010 at 3:09 PM, Daniel Spiewak
> > wrote:
> >
> > > I vote +1 on the next release being 1.4.0.
;
> On Sat, Feb 27, 2010 at 3:09 PM, Daniel Spiewak
> wrote:
>
> > I vote +1 on the next release being 1.4.0. I would also like to propose
> > another major new feature for the release: continuous compilation. This
> is
> > sitting in a basically-complete form in my GitH
On Sat, Feb 27, 2010 at 3:08 PM, Antoine Toulme wrote:
> OK for me - I guess the big improvement on that release would also be a
> standalone version with jruby ?
>
Good question. Given that JRuby is not licensed under ASL, this will have
to be somewhat separate from the official Apache release.
branch somewhere...
alex
On Sat, Feb 27, 2010 at 3:09 PM, Daniel Spiewak wrote:
> I vote +1 on the next release being 1.4.0. I would also like to propose
> another major new feature for the release: continuous compilation. This is
> sitting in a basically-complete form in my GitHub fo
o
> > vote and update the site with an updated tagline (I dropped the ball on
> > that
> > since December) and deal with some updates/changes on the release side
> > (gemcutter).
> >
> > How does that sound? Are we ready to call the next release 1.4.0?
> >
> > alex
> >
>
I vote +1 on the next release being 1.4.0. I would also like to propose
another major new feature for the release: continuous compilation. This is
sitting in a basically-complete form in my GitHub fork. I've been
dogfooding it for several months now, and it seems pretty solid. The only
t; vote and update the site with an updated tagline (I dropped the ball on
> that
> since December) and deal with some updates/changes on the release side
> (gemcutter).
>
> How does that sound? Are we ready to call the next release 1.4.0?
>
> alex
>
27/28th.
This should leave us enough time to round up a few more issues, some time to
vote and update the site with an updated tagline (I dropped the ball on that
since December) and deal with some updates/changes on the release side
(gemcutter).
How does that sound? Are we ready to call the nex
22 matches
Mail list logo
