[pskmail] Re: State of the windows pskmail server attempt
- From: Per Crusefalk <per@xxxxxxxxxxxx>
- To: pskmail@xxxxxxxxxxxxx
- Date: Thu, 29 Sep 2011 22:39:04 +0200
Hi,
The status now is that I have started over from the beginning.
My initial attempt was of the brute force kind where I wanted to
overcome as many obstacles as possible as fast as possible.
My idea was that I wanted to find out if it was at all possible and if
so then do the thing properly later.
At the moment I am taking a break as I have come pretty far but have
encountered the wall of perl panic. I have to add more logging to find
out where the issue is.
The server starts up, connects to big ear, connects to fldigi and starts
listening for traffic. It does not connect to aprs and for some strange
reason I have to reset variables here and there...
It's still in the hardcoded state, home is c:\pskmail and program dir is
c:\program\pskmail_server\. I could never get the $ENV{"HOME"} =
$ENV{"USERPROFILE"}; to work or some other thing is making it not load
pskmailrc.pl etc. I could only get it to work with absolute paths.
But, I now have a perl panic to handle so somewhere something is not
happy. Doesn't say where...:-(.
73 de Per, sm0rwo
tor 2011-09-29 klockan 14:27 -0400 skrev David Westbrook:
> The File::HomeDir module will make all of that stuff portable ...
> (Also employing File::Spec, File::Path, File::Basename, etc will
> really help with the portability.)
>
> For installation, maybe a bundle module to pull down all the CPAN deps
> would help ...
>
>
> I'd also be interested in trying to compile it with PAR to make a
> distributable .exe
>
> I'm a perl programmer (hobby & job) -- would be happy to help with a
> port .. can you email me off-list (dwestbrook@xxxxxxxxx) with the
> current windows perl code?
>
> --david
> KJ4IZW
>
> On Thu, Sep 29, 2011 at 12:23 PM, Per Crusefalk <per@xxxxxxxxxxxx>
> wrote:
> Thanks Klaus,
>
> I had replaced those HOME with a hardcoded path but the
> userprofile
> thing is good, will try that instead!
>
> 73!
>
> tor 2011-09-29 klockan 12:38 +0200 skrev Klaus Lohmann:
>
> > Per, this remark is probably redundant as you know it all
> already. What
> > I remember from a little project years ago:
> >
> > In case of Windows : $ENV{"HOME"} = $ENV{"USERPROFILE"};
> makes HOME
> > available.
> >
> > .pskmail as a directory should work, see .netbeans and
> others.
> >
> > The directory separators should be handled by perl if they
> are used
> > within paths.
> >
> > The main work will be the system() code of course.
> >
> > 73, Klaus
> >
> >
> > Am 29.09.2011 09:16, schrieb Per Crusefalk:
> > > Hi all,
> > >
> > > As many were asking for a windows version of the server I
> decided I
> > > should attempt to run it on a windows pc. As I am at the
> moment in a bit
> > > of a hurry (leaving for work) I will be very brief about
> where I am with
> > > that effort at the moment.
> > >
> > > So what am I trying exactly? Well, I am trying to create
> an installer
> > > for the standard perl pskmail server. Its not a port to
> java or any
> > > other environment but an attempt to get the server running
> in a native
> > > windows environment. With native I mean not in a virtual
> machine or
> > > within cygwin.
> > >
> > > So what have I done so far?
> > > - I have perl running on windows
> > > - I have a special windows installer for the server. It
> sets up the
> > > directories and gets the necessary modules through cpan.
> > > - I have overcome several obstacles that the windows
> environment happily
> > > provides. With that I mean that ENV{HOME} does not work,
> folder .pskmail
> > > does not work. I had an issue with directory separation (\
> or /).
> > > - Gotten gnu tools to run properly (windows versions of
> necessary unix
> > > tools like touch etc).
> > > - Replaced some things that aren't available on windows,
> like cat (which
> > > is type there but it's not as good).
> > >
> > > The state at this very moment is that the server runs but
> I have issues
> > > with loading and parsing of configuration (pskmailrc.pl).
> > >
> > > So, I am quite confident that it is possible to run the
> server on
> > > windows but it will impact the standard server in some
> ways. I have to
> > > get the environment stuff to work (like ENV{HOME} etc) and
> all the
> > > hardcoded paths will have to be made more general etc.
> > >
> > > The end result could be a server that runs on both linux
> and windows.
> > > The windows version will need a special installer of
> course but
> > > installjammer is good for such things. But, it will take
> some time as I
> > > have not gotten completely all the errors and warnings
> yet.... There
> > > will be more issues further down the road..
> > >
> > > 73 de Per, sm0rwo
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
>
>
>
Other related posts:
