July 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo Launcher 1.9.1 released

by Esteban Maringolo

On Mon, Jul 8, 2019 at 9:39 AM Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Hi Esteban, > > > Le 8 juil. 2019 Ã 14:24, Esteban Maringolo <emaringolo(a)gmail.com> a Ã©crit : > > > > Thanks, > > > > I downloaded the latest one for Windows, and it seems to work, but the > > "About" says Pharo Launcher is 1.6. > > Strange because the version is set during the build on the CI server: ./pharo PharoLauncher.image eval --save 'PhLAboutCommand version: '\â'1.9.1'\''' > > > Looking at the installation directory at > > <C:\Users\Esteban\AppData\Local\PharoLauncher\> the right files are > > there, so it's just a matter of the text in the About dialog. > > Are you sure, you use the right version? To ensure, by using shif+entre in PharoLauncher, you should see OSWSWinProcess class. I am sure, and also checked, because you never know... and the installer copied the files in the same directory as the previous one, but didn't overwrite them. So I uninstalled the previous version and re-installed the latest one and now it works fine (and faster, it seems). Which makes me suspicious about whether the 1.8 was installed at all last time I did it. Thank you! Esteban A. Maringolo

July 8, 2019

Re: [Pharo-dev] [ANN] OSWinSubprocess a library to spawn Windows System processes

by Christophe Demarey

Hi CÃ©dric, > Le 8 juil. 2019 Ã 12:39, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : > > Hi, > > Really nice Christophe. > > I wonder then if OSSubProcess shroud be Â« renamed Â» OSUnixSubProcess ? In my vision, I would like to see OsWinSubprocess merged into OSSubprocess once we have full support (e.g. std input/outputs). > A related question is the the limitation of LibC, iow. When to use LibC or the couple OSSubProcess/OSWinSubProcess ? Basically, OSSubprocess uses LibC and OSWinSubprocess uses the windows equivalent of LibC (Kernel32 and msvcrt). I would say it is easier to use a more high level library like OSSubprocess or OSWinSubprocess but it is still possible to use LibC directly. They can be used independently. On Windows, to workaround std input/output support you could just make the launched program write into a file and read it afterwards from Pharo. Also I think OSWinSubprocess is the only process library working on 64-bit images. HTH, Christophe.

July 8, 2019

Re: [Pharo-dev] [ANN] Pharo Launcher 1.9.1 released

by Christophe Demarey

Hi Esteban, > Le 8 juil. 2019 Ã 14:24, Esteban Maringolo <emaringolo(a)gmail.com> a Ã©crit : > > Thanks, > > I downloaded the latest one for Windows, and it seems to work, but the > "About" says Pharo Launcher is 1.6. Strange because the version is set during the build on the CI server: ./pharo PharoLauncher.image eval --save 'PhLAboutCommand version: '\â'1.9.1'\''' > Looking at the installation directory at > <C:\Users\Esteban\AppData\Local\PharoLauncher\> the right files are > there, so it's just a matter of the text in the About dialog. Are you sure, you use the right version? To ensure, by using shif+entre in PharoLauncher, you should see OSWSWinProcess class. Thanks for the feedback, Christophe.

July 8, 2019

Re: [Pharo-dev] [ANN] Pharo Launcher 1.9.1 released

by Esteban Maringolo

Thanks, I downloaded the latest one for Windows, and it seems to work, but the "About" says Pharo Launcher is 1.6. Looking at the installation directory at <C:\Users\Esteban\AppData\Local\PharoLauncher\> the right files are there, so it's just a matter of the text in the About dialog. Regards, Esteban A. Maringolo On Mon, Jul 8, 2019 at 5:33 AM Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Hi all, > > We are pleased to announce Pharo Launcher 1.9.1 release! > The goal of this release is to have a better Windows support. Indeed Pharo Launcher now uses a new library OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess) created for Pharo Launcher needs. This library allows to create Windows processes through ffi calls to the Windows API. It uses the unicode api, allowing paths with non-ascii characters. > In the same time, we switched from OSProcess to OSSubprocess (Linux and OS X) that is now the preferred library to use to fork processes on Linux-based systems. > > This release is not yet the default download of Pharo Launcher on Pharo web site because we want more feedback before promoting it. > Please use this link to install it: https://files.pharo.org/pharo-launcher/1.9 and let us know if this version works fine/better for you. > > ps: For now, the binary is not signed but it will come soon. > ps2: Thanks to Keldon Alleyne for his PR on Pharo Launcher offering the first FFI binding to Windows process API > > Regards, > The Pharo team. >

July 8, 2019

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher 1.9.1 released

by Christophe Demarey

Better with the right url: https://files.pharo.org/pharo-launcher/1.9.1 <https://files.pharo.org/pharo-launcher/1.9.1> > Le 8 juil. 2019 Ã 10:32, Christophe Demarey <christophe.demarey(a)inria.fr> a Ã©crit : > > Hi all, > > We are pleased to announce Pharo Launcher 1.9.1 release! > The goal of this release is to have a better Windows support. Indeed Pharo Launcher now uses a new library OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess <https://github.com/pharo-contributions/OSWinSubprocess>) created for Pharo Launcher needs. This library allows to create Windows processes through ffi calls to the Windows API. It uses the unicode api, allowing paths with non-ascii characters. > In the same time, we switched from OSProcess to OSSubprocess (Linux and OS X) that is now the preferred library to use to fork processes on Linux-based systems. > > This release is not yet the default download of Pharo Launcher on Pharo web site because we want more feedback before promoting it. > Please use this link to install it: https://files.pharo.org/pharo-launcher/1.9 <https://files.pharo.org/pharo-launcher/1.9> and let us know if this version works fine/better for you. > > ps: For now, the binary is not signed but it will come soon. > ps2: Thanks to Keldon Alleyne for his PR on Pharo Launcher offering the first FFI binding to Windows process API > > Regards, > The Pharo team. >

July 8, 2019

[Pharo 8.0] Build #453: Adding platform specific initialization for OSX

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #453 was: FAILURE. The Pull Request #3798 was integrated: "Adding platform specific initialization for OSX" Pull request url: https://github.com/pharo-project/pharo/pull/3798 Issue Url: https://github.com/pharo-project/pharo/issues/hiding Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 8, 2019

Re: [Pharo-dev] [ANN] OSWinSubprocess a library to spawn Windows System processes

by CÃ©drick BÃ©ler

Hi, Really nice Christophe. I wonder then if OSSubProcess shroud be Â« renamed Â» OSUnixSubProcess ? A related question is the the limitation of LibC, iow. When to use LibC or the couple OSSubProcess/OSWinSubProcess ? Cheers, CÃ©drik > Le 8 juil. 2019 Ã 12:13, Christophe Demarey <christophe.demarey(a)inria.fr> a Ã©crit : > > Hi, > > Pharo Launcher had stability problems to spawn new processes (launch Pharo images) on Windows as well as limitations (paths could only contain ASCII characters). > To solve this problem, we developed a new library: OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess <https://github.com/pharo-contributions/OSWinSubprocess>) and decided to make it a standalone library so that people can use it if they need to. > We tried to use the same API as OSSubprocess when possible. This library uses the Windows API to create process from both 32-bit and 64-bit Pharo images. It also supports Unicode characters. > > Here are some examples on how to use it: > process := OSWSWinProcess new > command: 'C:\Windows\notepad.exe'; > run. > ... > process terminate. > > OSWSWinProcess new > command: 'C:\Windows\notepad.exe'; > arguments: #('notepad.exe' 'C:\foo.txt'); > runAndWait. > Important note: As of now, this library does not yet support standard streams (stdin, stdout and stderr). It could be done by setting the appropriate information in the STARTUPINFO structutre. > > You can check the README for more information. > > Regards, > Christophe.

July 8, 2019

[Pharo 8.0] Build #452: FAILURE

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #452 was: FAILURE. Could not extract further issue information from commit message: Update weekly-digest.yml Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 8, 2019

[ANN] OSWinSubprocess a library to spawn Windows System processes

by Christophe Demarey

Hi, Pharo Launcher had stability problems to spawn new processes (launch Pharo images) on Windows as well as limitations (paths could only contain ASCII characters). To solve this problem, we developed a new library: OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess <https://github.com/pharo-contributions/OSWinSubprocess>) and decided to make it a standalone library so that people can use it if they need to. We tried to use the same API as OSSubprocess when possible. This library uses the Windows API to create process from both 32-bit and 64-bit Pharo images. It also supports Unicode characters. Here are some examples on how to use it: process := OSWSWinProcess new command: 'C:\Windows\notepad.exe'; run. ... process terminate. OSWSWinProcess new command: 'C:\Windows\notepad.exe'; arguments: #('notepad.exe' 'C:\foo.txt'); runAndWait. Important note: As of now, this library does not yet support standard streams (stdin, stdout and stderr). It could be done by setting the appropriate information in the STARTUPINFO structutre. You can check the README for more information. Regards, Christophe.

July 8, 2019

[Pharo 8.0] Build #451: 3812-remove-testAllReferencesToPool

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #451 was: SUCCESS. The Pull Request #3813 was integrated: "3812-remove-testAllReferencesToPool" Pull request url: https://github.com/pharo-project/pharo/pull/3813 Issue Url: https://github.com/pharo-project/pharo/issues/3812 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 8, 2019