List Info

Thread: Orphaned modules (was: compiling Inline::Ruby on win32)




Orphaned modules (was: compiling Inline::Ruby on win32)
country flaguser name
Canada
2007-08-10 16:45:41
hmm..

So -- ruby uses 'native' signals on win32 and perl rolls it
own? Is that the major issue?
Too bad.. it would be awfully nice to be able to 'borrow'
any APIs that ruby folks 
write, and roll them up into CPAN.

Anyways, apparently HttpWatch has a generic COM interface
(not a ruby-only) extension, 
so I was going to write perl around that, but I'm running
into other issues. 


In particular, it looks like Win32::Setupsup and Win32::SAM
are both sort of 
orphaned modules that are fairly essential to controlling
internet explorer in 
a fine, granularized way (ie: firing up IE and populating
both main windows and closing
popups), so I was hoping that I could get those working.


However, both don't seem to have ppms, and setupsup is not
even listed on CPAN
(although after doing some grepping I see you can get it at

(http://www.cpan.org/modules/by-module/Win32/setu
psup.1.0.1.0.zip)

Does anyone have an idea whether these are going to make it
to ppms for 5.8? 
I also see that setupsup in particular requires a SDK.  Is
there a separate 
requirement that I need to compile this, or is visualc++ 6.0
sufficient?


Thanks,

Ed

On Fri, Aug 10, 2007 at 05:22:12PM +1000, Sisyphus wrote:
> 
> ----- Original Message ----- 
> From: "Ed S. Peschko" <esp5pge.com>
> To: <Joerelay.fibrehost.net>
> Cc: "Jan Dubois" <jandactivestate.com>; "Eric Promislow" 
> <ericpactivestate.com>; "Gisle Aas"
<gisleactivestate.com>; 
> <perl-win32-userslistserv.ActiveState.com>; "Todd
Whiteman" 
> <toddwactivestate.com>
> Sent: Thursday, August 09, 2007 4:15 PM
> Subject: [SPAM?] Compilation of Inline::Ruby on win32
> 
> 
> >All,
> >
> >I'm trying to compile Inline::Ruby on win32, using
visualc++ v6 and
> >activestate perl, without too much luck, in trying
to get HttpWatch
> >to work with perl.
> >
> >In particular, I'm having difficulty with the
headers.
> 
> As it stands, signal.h and Win32 perl are incompatible.
You can't #include 
> <signal.h> on Win32 when building perl
extensions. And I think signal.h 
> gets pulled in as soon as you #include
"ruby.h".
> 
> So it looks like an impasse to me - though, faik, it
may be possible to 
> hack your way through it.
> 
> ---------------------------------------
> C:_32pscrptinline>type try.pl
> 
> use warnings;
> 
> use Inline C => <<'EOC';
> 
> #include <signal.h>
> 
> void foo() {
>     printf("Hello Worldn");
> }
> 
> EOC
> 
> foo();
> 
> C:_32pscrptinline>perl try.pl
> .
> <snipped>
> .
> In file included from try_pl_3fe7.xs:6:
>
C:/_32/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../includ
e/signal.h:84: 
> error: syntax error before '(' token
> dmake:  Error code 129, while making 'try_pl_3fe7.o'
> .
> <snipped>
> .
> BEGIN failed--compilation aborted at try.pl line 12.
> 
> ---------------------------------------
> 
> I could find ppm's for many of the Inline: modules,
but not Inline::Ruby 
> - which also is not a good sign.
> 
> Cheers,
> Rob 
> 
_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Userslistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs


_______________________________________________
ActivePerl mailing list
ActivePerllistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )