- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] get.pharo.org scripts don't works on windows?

by Gabriel Cotelli

Give it a try on an empty folder... I think that fails if you already have the VM or image. On Tue, Apr 1, 2014 at 12:30 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > (run under mingw sheel) > > curl get.pharo.org/vmLatest | bash > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 5309 100 5309 0 0 129k 0 --:--:-- --:--:-- --:--:-- > 259k > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/win/latest.zip > pharo-vm/Pharo.exe > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Creating starter scripts pharo and pharo-ui > bash: line 115: pharo: File exists > > -- > Best regards, > Igor Stasenko. >

April 1, 2014

Re: [Pharo-dev] get.pharo.org scripts don't works on windows?

by Igor Stasenko

meh... :( as in meh.com On 1 April 2014 17:41, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Works here. > > > User@Techlab ~/Experiments/igor > $ curl get.pharo.org/vmLatest | bash > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 5309 100 5309 0 0 13612 0 --:--:-- --:--:-- --:--:-- > 13612 > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/win/latest.zip > pharo-vm/Pharo.exe > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Creating starter scripts pharo and pharo-ui > > On Tue, Apr 1, 2014 at 5:30 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> (run under mingw sheel) >> >> curl get.pharo.org/vmLatest | bash >> % Total % Received % Xferd Average Speed Time Time Time >> Current >> Dload Upload Total Spent Left >> Speed >> 100 5309 100 5309 0 0 129k 0 --:--:-- --:--:-- --:--:-- >> 259k >> Downloading the latest pharoVM: >> http://files.pharo.org/vm/pharo/win/latest.zip >> pharo-vm/Pharo.exe >> Downloading PharoV10.sources: >> http://files.pharo.org/sources//PharoV10.sources.zip >> Downloading PharoV20.sources: >> http://files.pharo.org/sources//PharoV20.sources.zip >> Creating starter scripts pharo and pharo-ui >> bash: line 115: pharo: File exists >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

April 1, 2014

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

by Igor Stasenko

okay i uploaded updated configs for NativeBoost and Athens into official repositories for these projects. Gofer new smalltalkhubUser: 'Pharo' project: 'NativeBoost'; configuration; load. ConfigurationOfNativeBoost loadDevelopment. Gofer new smalltalkhubUser: 'Pharo' project: 'Athens'; configuration; load. ConfigurationOfAthens loadDevelopment. shall do the trick.. for more details see https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-diffe… On 28 March 2014 21:13, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > thanks Igor. > Iâm trying to look at the font reloading bug. > > > On 28 Mar 2014, at 17:19, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-diffe… > > > On 28 March 2014 16:42, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> so, the quick and dirty fix is to put: >> >> CairoGlyph class>>byteAlignment >> >> NativeBoost platformId = NativeBoostConstants win32PlatformId ifTrue: >> [ ^ 8 ]. >> ^ super byteAlignment >> >> and then: >> >> CairoGlyph rebuildFieldAccessors >> CairoGlyphsArray initialize >> >> (note you must run this snippet each time your image changes platform).. >> >> and i need more time to fix it for real, because it is NB issue, to >> automatically recalculate the structs size >> if it changes platform.. (which also means you cannot store instances of >> struct in image which survive the session) >> ... damn.. that's going to be complicated. >> >> --- >> >> >> >> On 28 March 2014 16:27, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> >>> >>> >>> On 28 March 2014 16:01, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>>> >>>> Ookkayy.. >>>> so, current status: >>>> >>>> - finally we got an agreement that big red square because of font >>>> loading issues and font rendering artifacts is two separate issues. >>>> Thanks! >>>> - i am not going to address font-loading issue here and now.. (because >>>> we spent time on it earlier today with Stef already and you should have the >>>> report on it in separate mail). >>>> >>>> - we seem to be agreed that it is best to use same (up-to-date version) >>>> of software when reporting issues to work on them. Thanks again. :) >>>> >>>> - while on linux and mac things seem to be working fine, i can confirm >>>> that there is rendering artifacts (same as reported by Vincent) on Windows. >>>> >>>> so i going to explore what causing this problem.. >>>> >>>> ... and found the cause: >>> >>> On windows, for unknown reason, the structure (cairo_glyph_t) uses >>> different memory space alignment than on mac and linux >>> >>> fieldsDesc >>> ^ #( >>> ulong index; >>> double x; >>> double y; >>> ) >>> >>> on mac and linux , the size of this structure in memory = 4 + 8 + 8 = 20 >>> bytes, >>> on windows, however, due to 8-byte alignment, it is 4 + 8 + 8 + (4 >>> alignment) bytes... >>> >>> this causing the effect that if you copy array of glyphs in memory, >>> it does not copying whole array by slightly less (because it uses wrong >>> struct size which is smaller than it is).. >>> and because of that, you got weird artefacts at the tail of string, >>> replaced by misplaced/invalid characters etc.. >>> because it is basically read from uninitialized part of memory with >>> random data. >>> >>> i going to fix structure alignment for windows from default 4 bytes to 8 >>> bytes.. >>> but this is not very good news.. because this affecting many things... >>> (as you can imagine, not only cairo/athens working with external >>> structures, which need to be properly aligned). >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Best regards, > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

April 1, 2014

Re: [Pharo-dev] PharoVM on Windows & Code::Blocks for debugging

by phil＠highoctane.be

Latest version fails to build. Scanning dependencies of target libssh2 [ 9%] Unpacking libssh2 ... [ 10%] Building libssh2 checking whether to enable maintainer-specific portions of Makefiles... no checking for sed... /bin/sed checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking libssh2 version... 1.4.3 checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 configure: autobuild project... libssh2 configure: autobuild revision... 1.4.3 configure: autobuild hostname... Techlab configure: autobuild timestamp... 20140401-173417 checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for long long... yes checking if _REENTRANT is already defined... no checking if _REENTRANT is actually needed... no checking if _REENTRANT is onwards defined... no checking for library containing socket... no checking for library containing inet_addr... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking whether ln -s works... no, using cp -pR checking whether make sets $(MAKE)... (cached) yes checking for sshd... no checking for as... as checking for dlltool... dlltool checking for objdump... objdump checking how to print strings... printf checking for a sed that does not truncate output... (cached) /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... c:/mingw/mingw32/bin/ld.exe checking if the linker (c:/mingw/mingw32/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /c/MinGW/bin/nm checking the name lister (/c/MinGW/bin/nm) interface... BSD nm checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-mingw32 file names to i686-pc-mingw32 format... func_convert_file_msys_to_w32 checking how to convert i686-pc-mingw32 file names to toolchain format... func_convert_file_msys_to_w32 checking for c:/mingw/mingw32/bin/ld.exe option to reload object files... -r checking for objdump... (cached) objdump checking how to recognize dependent libraries... file_magic ^x86 archive import|^x86 DLL checking for dlltool... (cached) dlltool checking how to associate runtime and link libraries... func_cygming_dll_for_implib checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /c/MinGW/bin/nm output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking for dlfcn.h... no checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -DDLL_EXPORT -DPIC checking if gcc PIC flag -DDLL_EXPORT -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (c:/mingw/mingw32/bin/ld.exe) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether byte ordering is bigendian... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... unknown checking for _LARGE_FILES value needed for large files... unknown checking for ld used by GCC... c:/mingw/mingw32/bin/ld.exe checking if the linker (c:/mingw/mingw32/bin/ld.exe) is GNU ld... yes checking for shared library run path origin... done checking for libssl... no checking for libgcrypt... no configure: error: cannot find OpenSSL or Libgcrypt, try --with-libssl-prefix=PATH or --with-libgcrypt-prefix=PATH make[2]: *** [thirdparty/out/bin/libssh2-1.dll] Error 1 make[1]: *** [thirdParty/libssh2/CMakeFiles/libssh2.dir/all] Error 2 make: *** [all] Error 2 User@Techlab ~/PharoVM/pharo-vm/build $ On Tue, Apr 1, 2014 at 2:34 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi, > > in last version of sources you have a > > #generateForDebug who prepares the sources for debugging. > Check in the PharoVMBuilder. > > Esteban > > > On 01 Apr 2014, at 09:02, phil(a)highoctane.be wrote: > > On Tue, Apr 1, 2014 at 1:22 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> Hi, >> >> I use CDT regularly (bah, its been like 6 months that I don't, but I use >> it when I need it :) ) >> It is not a problem with the current configuration (and debug flags), but >> is a bit of work for adding the source paths. >> >> I do not know if it can be done easier... would be cool, but I don't know >> how feasible :) >> >> Esteban >> > > Now, I managed to get GDB to work with my build. > > I had to change the compile options a bit (-g -O0) in the code generation > and add a couple of source folders in the .gdbinit file to get the sources > to show: > > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/src/plugins > directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/src/vm > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32 > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross/vm > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross/plugins > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32/vm > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32/plugins > break sqMain > > Now it works. > > But that's not really funny to work like that, so, back to the UI > integration. > > Esteban, do you debug with CDT with the current flags? > > compilerFlagsRelease > "Define NDEBUG for production to exclude asserts " > ^ '-g0 -O2 -march=pentium4 -momit-leaf-frame-pointer > -maccumulate-outgoing-args -funroll-loops ', > '-DNDEBUG -DDEBUGVM=0' > > > for debugging I've set things to: > > compilerFlagsDebug > "Define NDEBUG for production to exclude asserts " > ^ '-g -O0 -march=pentium4 ', > '-DNDEBUG -DDEBUGVM=0' > > and > > compilerFlags > "depends on config ..." > ^ self commonCompilerFlags, ' ' , self compilerFlagsDebug "was Release" > > I've checked that the flags were right with building with > > make VERBOSE=1 > > in the build.sh > > I am interested in looking at the startup process for the VM and getting a > real windows headless system. > The current one isn't working at the moment. Also, the pharo as a service > should work again (is now with -DNO_SERVICE in the compilation) > > I've noticed that the OSX Version supports debug options, but not Windows. > Am I right? > > Phil > > >> >> On 01 Apr 2014, at 03:56, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> >> I'd like to know if someone managed to get Code::Blocks to work with >> the >> >> MinGW configuration. >> > >> > No - but I think it would be good if there would be a preconfigured >> project >> > for easy debugging with Eclipse CDT (C/C++ Development Tooling). >> > >> > Thx >> > T. >> > >> > >> >> >> > <DBG01-04-14 13-16-17.png> > > >

April 1, 2014

Re: [Pharo-dev] get.pharo.org scripts don't works on windows?

by phil＠highoctane.be

Works here. User@Techlab ~/Experiments/igor $ curl get.pharo.org/vmLatest | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 5309 100 5309 0 0 13612 0 --:--:-- --:--:-- --:--:-- 13612 Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/win/latest.zip pharo-vm/Pharo.exe Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui On Tue, Apr 1, 2014 at 5:30 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > (run under mingw sheel) > > curl get.pharo.org/vmLatest | bash > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 5309 100 5309 0 0 129k 0 --:--:-- --:--:-- --:--:-- > 259k > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/win/latest.zip > pharo-vm/Pharo.exe > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Creating starter scripts pharo and pharo-ui > bash: line 115: pharo: File exists > > -- > Best regards, > Igor Stasenko. >

April 1, 2014

get.pharo.org scripts don't works on windows?

by Igor Stasenko

(run under mingw sheel) curl get.pharo.org/vmLatest | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 5309 100 5309 0 0 129k 0 --:--:-- --:--:-- --:--:-- 259k Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/win/latest.zip pharo-vm/Pharo.exe Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui bash: line 115: pharo: File exists -- Best regards, Igor Stasenko.

April 1, 2014

MOOSEDay@UPMC : Talks & Registration

by Serge Stinckwich

Dear all, just a reminder. We will organize a MOOSEDay at Paris June 5th and 6th. You will find more information about the two days here: http://www.doesnotunderstand.org/MOOSEDayUPMC/ We have currently 2 presentations and 6 registrations. You can register online, this is free ;-) Thanks to our sponsors (ESUG, ObjectProfile & UMMISCO), the lunches will be free. This is your conference and we really need more talks. If you want to present your work, please send me a title and a short description. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 1, 2014

Re: [Pharo-dev] New Nautilus side bar buttons

by Benjamin

On 01 Apr 2014, at 14:01, Stephan Eggermont <stephan(a)stack.nl> wrote: > Ah, thatâs easy. > Putting them into a plugin is left as an exercise for the reader. As well as implementing the support for plugin on sides and not only top/middle/bottom Remind me a lot of lectures I had: âToday we will see how to go on the Moon. â¦ This was how to fill up the tank, the rest is left as an exerciseâ Ben

April 1, 2014

Re: [Pharo-dev] PharoVM on Windows & Code::Blocks for debugging

by phil＠highoctane.be

Ok. I was working from my fork. Needs to pull on some new stuff. Phil Le 1 avr. 2014 14:35, "Esteban Lorenzano" <estebanlm(a)gmail.com> a Ã©crit : > Hi, > > in last version of sources you have a > > #generateForDebug who prepares the sources for debugging. > Check in the PharoVMBuilder. > > Esteban > > > On 01 Apr 2014, at 09:02, phil(a)highoctane.be wrote: > > On Tue, Apr 1, 2014 at 1:22 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> Hi, >> >> I use CDT regularly (bah, its been like 6 months that I don't, but I use >> it when I need it :) ) >> It is not a problem with the current configuration (and debug flags), but >> is a bit of work for adding the source paths. >> >> I do not know if it can be done easier... would be cool, but I don't know >> how feasible :) >> >> Esteban >> > > Now, I managed to get GDB to work with my build. > > I had to change the compile options a bit (-g -O0) in the code generation > and add a couple of source folders in the .gdbinit file to get the sources > to show: > > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/src/plugins > directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/src/vm > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32 > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross/vm > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross/plugins > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32/vm > directory > C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32/plugins > break sqMain > > Now it works. > > But that's not really funny to work like that, so, back to the UI > integration. > > Esteban, do you debug with CDT with the current flags? > > compilerFlagsRelease > "Define NDEBUG for production to exclude asserts " > ^ '-g0 -O2 -march=pentium4 -momit-leaf-frame-pointer > -maccumulate-outgoing-args -funroll-loops ', > '-DNDEBUG -DDEBUGVM=0' > > > for debugging I've set things to: > > compilerFlagsDebug > "Define NDEBUG for production to exclude asserts " > ^ '-g -O0 -march=pentium4 ', > '-DNDEBUG -DDEBUGVM=0' > > and > > compilerFlags > "depends on config ..." > ^ self commonCompilerFlags, ' ' , self compilerFlagsDebug "was Release" > > I've checked that the flags were right with building with > > make VERBOSE=1 > > in the build.sh > > I am interested in looking at the startup process for the VM and getting a > real windows headless system. > The current one isn't working at the moment. Also, the pharo as a service > should work again (is now with -DNO_SERVICE in the compilation) > > I've noticed that the OSX Version supports debug options, but not Windows. > Am I right? > > Phil > > >> >> On 01 Apr 2014, at 03:56, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> >> I'd like to know if someone managed to get Code::Blocks to work with >> the >> >> MinGW configuration. >> > >> > No - but I think it would be good if there would be a preconfigured >> project >> > for easy debugging with Eclipse CDT (C/C++ Development Tooling). >> > >> > Thx >> > T. >> > >> > >> >> >> > <DBG01-04-14 13-16-17.png> > > >

April 1, 2014

Re: [Pharo-dev] Font problem identified

by Igor Stasenko

On 1 April 2014 14:56, Ben Coman <btc(a)openinworld.com> wrote: > I only did the simplest thing that I could think of. I now notice it > has the downside of dirtying the package. I'll have a go at pragma > solution. What would you suggest to name the pragma? <embeddedFont> ? > > <embeddedFontS> or <extraFontS> and method should take an argument - the font manager instance, so the method's implementor can control the way how to register fonts.. else if it will be <embeddedFont> then it will imply that method will have to answer a single instance of single font... which will mean, you'll have to implement a method per each font.. which is not always a good way, in case if you want a centralized control over registering a bunch of fonts at once, instead of duplicating same code over may methods. > cheers -ben > > -- Best regards, Igor Stasenko.

April 1, 2014