Windows build

46 views
Skip to first unread message

L Michaels

unread,
Dec 1, 2016, 3:35:10 PM12/1/16
to xpost-discuss
According to http://luser-dr00g.github.io/xpost/:
>a windows build cannot run because there's no installer to coordinate the location for the postscript-language data files that are needed.

Tried building with mingw and msys.  I have fontconfig and some basic fonts installed, so it should be able to find some fonts.  The code appears to be looking for the .ps files in ../share/xpost, so it should be able to find that.  Is there anything else that would need to be fixed for a Windows build?  I tried viewing the output of the lcal program and it brought up a couple of circles, but that was it.

I'm trying to find a Postscript viewer and replacement for Ghostscript.  Was hoping xpost might be able to do the job.

Thanks.




Vincent Torri

unread,
Dec 1, 2016, 4:46:50 PM12/1/16
to L Michaels, xpost-discuss
Hello

On Thu, Dec 1, 2016 at 9:35 PM, L Michaels <lme...@gmail.com> wrote:
> According to http://luser-dr00g.github.io/xpost/:
>>a windows build cannot run because there's no installer to coordinate the
>> location for the postscript-language data files that are needed.
>
> Tried building with mingw and msys. I have fontconfig and some basic fonts
> installed, so it should be able to find some fonts. The code appears to be
> looking for the .ps files in ../share/xpost, so it should be able to find
> that. Is there anything else that would need to be fixed for a Windows
> build? I tried viewing the output of the lcal program and it brought up a
> couple of circles, but that was it.

You need freetype and fontconfig, indeed. MSYS + MinGW is fine, though
i would suggest MSYS2 + Win-Builds.

there are some problems with some Postscript files (missing operators)
but it runs fine otherwise

> I'm trying to find a Postscript viewer and replacement for Ghostscript. Was
> hoping xpost might be able to do the job.

I have begun to write a very simple viewer (look at xpost_view* in
src/bin) but there is a little problem i can't fix for now (i just
have a blank page...)

I'm also writing a multi document program (like okular or evince) and
I want to use xpost as the licence of ghostscript is too restrictive
for me

regards

Vincent Torri

luserdroog .

unread,
Dec 1, 2016, 7:08:55 PM12/1/16
to xpost-discuss

Forgot to reply-all. :)

---------- Forwarded message ----------
From: "luserdroog ." <luser...@gmail.com>
Date: Dec 1, 2016 3:07 PM
Subject: Re: [xpost-discuss] Windows build
To: "L Michaels" <lme...@gmail.com>
Cc:

I think that's the only thing missing that's needed for a windows build. And that's just MSVC builds that need it. With msys you should be able to do `make install` and then run it from the command line.

There are other issues with the postscript interpretation we're still working on. And image quality.


--
You received this message because you are subscribed to the Google Groups "xpost-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xpost-discuss+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/xpost-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/xpost-discuss/1dfad44c-e3c6-4c87-baa3-14ada4aea94a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

vincent.torri

unread,
Dec 2, 2016, 8:06:41 AM12/2/16
to xpost-discuss
hey


Le vendredi 2 décembre 2016 01:08:55 UTC+1, luserdroog a écrit :

Forgot to reply-all. :)

---------- Forwarded message ----------
From: "luserdroog ." <luser...@gmail.com>
Date: Dec 1, 2016 3:07 PM
Subject: Re: [xpost-discuss] Windows build
To: "L Michaels" <lme...@gmail.com>
Cc:

I think that's the only thing missing that's needed for a windows build. And that's just MSVC builds that need it. With msys you should be able to do `make install` and then run it from the command line.


maybe environment variables can help

Vincent

L Michaels

unread,
Dec 2, 2016, 8:21:54 AM12/2/16
to xpost-discuss
Thanks for the information on building for Windows.


Vincent Torri wrote:

>You need freetype and fontconfig, indeed. MSYS + MinGW is fine, though
>i would suggest MSYS2 + Win-Builds.

I do my own custom builds and have my own build system, utilites and scripts.  I have a copy of the MinGW compiler (from the MinGW.org project), but I also have my own build of MinGW with POSIX threading enabled by default and other modifications.  I also use several BSD utilities and am slowly trying to replace MSYS with Win32 native versions of utilities that don't rely on a Cygwin fork to run.  My build of fontconfig includes some patches that let it run more like it does on Linux and Unix systems and doesn't require any registry settings.  I run a lot of portable apps (portable as in cross-platform, but also portable as in easy to move from computer to computer via flash drive).


>I have begun to write a very simple viewer (look at xpost_view* in
>src/bin) but there is a little problem i can't fix for now (i just
>have a blank page...)

Will check it out.  Thanks.

Was thinking a lightweight SDL based viewer might be a nice, cross-platform portable option.  Might try coding something once I get a better feel for the xpost software and how it works.

Saw a mention of SVG in a few of the xpost-discuss posts.  May not be useful, but I thought I'd mention the nanosvg code ( https://github.com/memononen/nanosvg ).  I've used it in a few projects that needed SVG support (like Tuxmath).

Hoping to find a cross-platform Postscript viewer that let's me view the output of programs like abcm2ps, lcal and pcal.  So far, Xpost looks more portable and more lightweight than Ghostscript.  The license differences sound like a nice plus too.  Wish you good luck with the project and if I can help with testing or something, let me know.

Sincerely,
Laura
http://www.distasis.com/cpp

luserdroog

unread,
Dec 2, 2016, 8:08:24 PM12/2/16
to xpost-discuss
Yes. Now that you mention it, I thought we did do that. Or at least we talked about it.

 $ grep DATA_DIR *[ch]
xpost_interpreter.c:    also creates the definitions PACKAGE_DATA_DIR PACKAGE_INSTALL_DIR and EXE_DIR
xpost_interpreter.c:    /* environment variable XPOST_DATA_DIR */
xpost_interpreter.c:    if ((path = getenv("XPOST_DATA_DIR")))
xpost_interpreter.c:#ifdef PACKAGE_DATA_DIR
xpost_interpreter.c:    path = PACKAGE_DATA_DIR;
xpost_interpreter.c:                 "/DATA_DIR (%s) def exec ", path_init_ps, path_init);

Yes. So on any platform, you can define the env variable XPOST_DATA_DIR as the path to the data directory where init.ps
and friends can be found. I had forgotten that we did this.

I should add this to the readme. So an installer isn't essential anymore,
but would make the process much easier.

luserdroog

unread,
Dec 2, 2016, 8:26:27 PM12/2/16
to xpost-discuss


On Friday, December 2, 2016 at 7:21:54 AM UTC-6, L Michaels wrote:
Thanks for the information on building for Windows.

Vincent Torri wrote:

>You need freetype and fontconfig, indeed. MSYS + MinGW is fine, though
>i would suggest MSYS2 + Win-Builds.

I do my own custom builds and have my own build system, utilites and scripts.  I have a copy of the MinGW compiler (from the MinGW.org project), but I also have my own build of MinGW with POSIX threading enabled by default and other modifications.  I also use several BSD utilities and am slowly trying to replace MSYS with Win32 native versions of utilities that don't rely on a Cygwin fork to run.  My build of fontconfig includes some patches that let it run more like it does on Linux and Unix systems and doesn't require any registry settings.  I run a lot of portable apps (portable as in cross-platform, but also portable as in easy to move from computer to computer via flash drive).


I'd agree that MSYS2 is significantly more supported. When I looked last,
MSYS does have all the bells and whistles now like a package manager,
but MSYS2 has that + lots of packages already available.

There's also this very enticing project from Kaz, which lets you develop
and deploy from Cygwin but with no dependencies:

 
>I have begun to write a very simple viewer (look at xpost_view* in
>src/bin) but there is a little problem i can't fix for now (i just
>have a blank page...)

Will check it out.  Thanks.

Was thinking a lightweight SDL based viewer might be a nice, cross-platform portable option.  Might try coding something once I get a better feel for the xpost software and how it works.

Saw a mention of SVG in a few of the xpost-discuss posts.  May not be useful, but I thought I'd mention the nanosvg code ( https://github.com/memononen/nanosvg ).  I've used it in a few projects that needed SVG support (like Tuxmath).

Hoping to find a cross-platform Postscript viewer that let's me view the output of programs like abcm2ps, lcal and pcal.  So far, Xpost looks more portable and more lightweight than Ghostscript.  The license differences sound like a nice plus too.  Wish you good luck with the project and if I can help with testing or something, let me know.

Sincerely,
Laura
http://www.distasis.com/cpp

Thanks. Were mostly looking for small postscript files from different
generators. Specifically ones that /fail/, so we can fix it! :) 

Josh (luserdroog)

vincent.torri

unread,
Dec 3, 2016, 5:06:41 AM12/3/16
to xpost-discuss


Le samedi 3 décembre 2016 02:26:27 UTC+1, luserdroog a écrit :


On Friday, December 2, 2016 at 7:21:54 AM UTC-6, L Michaels wrote:
Thanks for the information on building for Windows.

Vincent Torri wrote:

>You need freetype and fontconfig, indeed. MSYS + MinGW is fine, though
>i would suggest MSYS2 + Win-Builds.

I do my own custom builds and have my own build system, utilites and scripts.  I have a copy of the MinGW compiler (from the MinGW.org project), but I also have my own build of MinGW with POSIX threading enabled by default and other modifications.  I also use several BSD utilities and am slowly trying to replace MSYS with Win32 native versions of utilities that don't rely on a Cygwin fork to run.  My build of fontconfig includes some patches that let it run more like it does on Linux and Unix systems and doesn't require any registry settings.  I run a lot of portable apps (portable as in cross-platform, but also portable as in easy to move from computer to computer via flash drive).


I'd agree that MSYS2 is significantly more supported. When I looked last,
MSYS does have all the bells and whistles now like a package manager,
but MSYS2 has that + lots of packages already available.

MSYS2 is also a lot faster than MSYS

Vincent
 

vincent.torri

unread,
Dec 9, 2016, 11:48:49 PM12/9/16
to xpost-discuss
Josh just fixed some bugs and xpost_view is displaying minimal PS file :)

there are still some problems with some PS files generated by dvips

Vincent
Reply all
Reply to author
Forward
0 new messages