Re: Update Windows binaries

Hi! > Pacman does allow you to pin versions just like you can in other package > management systems (like apt). You do that like pacman -S bash==3.2. But > obviously the pinned version must be available in the repos used. After trying this locally I'm not sure that installing non-last package

Re: Update Windows binaries

On 19 May 2018 at 05:46, Vasily Galkin wrote: > Hello again! > Due to recent pangocairo changes in mingw-msys2 meld 3-18 become incompatible > with it (even running from checkout). Honestly, I think it's unlikely that moving 3.18 to msys2 is worth it. The current Windows

Re: Update Windows binaries

Hello again! Due to recent pangocairo changes in mingw-msys2 meld 3-18 become incompatible with it (even running from checkout). So I cherrypicked last changes Keegan Witt made for 3-18 (thanks!) changes to new branch created from current master, fix pangocairo and make some more adjustments:

Re: Update Windows binaries

Ah. Thanks Vasily! I pushed some more changes, both builds are producing an msi now. Unfortunately, both are also still producing the error Microsoft Visual C++ Runtime Library Runtime Error! Program: C:Program Files (x86)MeldMeld.exe This application has requested the Runtime to terminate it

Re: Update Windows binaries

> I wasn't actually running the YAML. I exported the YAML then edited it to > match what I was experimenting with in the UI (it seemed to ignore my YAML > anyway -- even when I set the YAML name). I think that for building from gitlab it should be set not to file name but to full url: like

Re: Update Windows binaries

I wasn't actually running the YAML. I exported the YAML then edited it to match what I was experimenting with in the UI (it seemed to ignore my YAML anyway -- even when I set the YAML name). The error window says cx_Freeze: Python error in main script Traceback (most recent call last): File

Re: Update Windows binaries

> I realize that, I just wasn't sure what components were associated with those > DLLs as of when the setup script was created. I got it to build locally > (though Meld exits with "application requested runtime to terminate in an > unusual way" after it's installed. On Appveyor it still fails

Re: Update Windows binaries

I realize that, I just wasn't sure what components were associated with those DLLs as of when the setup script was created. I got it to build locally (though Meld exits with "application requested runtime to terminate in an unusual way" after it's installed. On Appveyor it still fails with

Re: Update Windows binaries

As far as a remember the DLL list that is hard-coded into setup_win32.py is specific to gtk version/distribution since in fact it lists not only DLLs that meld loads via pygobject interface but all their dependencies too. For example list content changed (both additions and deletions) with last

Re: Update Windows binaries

I'm working on getting this running locally in MSYS2 now. It looks like the DLLs are in /mingw32/bin/ instead of Python's sites-packages directory. There's 2 DLLs I'm missing though libzzz.dll libxmlxpat.dll Do you know what these are? I'm having trouble finding the package that will install

Re: Update Windows binaries

Installing mingw-w64-i686-python3-cx_Freeze instead of installing through pip gets around the compilation problem, but then I again hit the error: invalid command 'bdist_msi' problem. I'm also wondering about the glib2-devel package. There's a msys2 package, but not a mingw32 or mingw64

Re: Update Windows binaries

It appears there's actually 3 different installations of Python 3 in MSYS2: mingw32 (/mingw32/bin/python3), mingw64 (/mingw64/bin/python3), and msys2 (/usr/bin/python3). To make sure we use the right version of Python, I set a MSYSTEM environment variable (I also tried with fully-qualified path

Re: Update Windows binaries

I tried again building without pywin32 and its definitely not required while building with msvc-built python on appveyour. There is only warning >running build_exe >creating directory build\exe.win32-3.4 >copying C:\Python34\lib\site-packages\cx_Freeze\bases\Win32GUI.exe ->

Re: Update Windows binaries

On 29 April 2018 at 05:19, Keegan Witt wrote: > I'm having trouble getting pywin32 installed in MSYS2. When I try to > install with pip, I get errors > $ python3 -m pip install pypiwin32==219 > Collecting pypiwin32==219 > Using cached >

Re: Update Windows binaries

On 29 April 2018 at 05:51, Keegan Witt wrote: > Kai, > Maybe we could change that line to get the element that has "site-packages" > in it? Seems reasonable! I just pushed this to master. cheers, Kai ___ meld-list mailing list

Re: Update Windows binaries

Are you sure pywin32 isn't required? When I edited the site-packages list, it wouldn't let me run the bdist_msi command bash -lc 'cd "%APPVEYOR_BUILD_FOLDER%" && sed --in-place --regexp-extended "s/site.getsitepackages\(\)\[1\]/site.getsitepackages()[-1]/" setup_win32.py' bash -lc 'cd

Re: Update Windows binaries

> Once I take out pypiwin32, then I run into the same issue as reported in the > "Building MSI package under MSYS" thread > bash -lc 'cd "%APPVEYOR_BUILD_FOLDER%" && glib-compile-schemas data && > python3 setup_win32.py bdist_msi' > > Traceback (most recent call last): > > File

Re: Update Windows binaries

Kai, Or I guess even simpler, just get the last element. On Sat, Apr 28, 2018 at 3:51 PM, Keegan Witt wrote: > Once I take out pypiwin32, then I run into the same issue as reported in > the "Building MSI package under MSYS" thread > bash -lc 'cd "%APPVEYOR_BUILD_FOLDER%"

Re: Update Windows binaries

Once I take out pypiwin32, then I run into the same issue as reported in the "Building MSI package under MSYS" thread bash -lc 'cd "%APPVEYOR_BUILD_FOLDER%" && glib-compile-schemas data && python3 setup_win32.py bdist_msi' Traceback (most recent call last): File "setup_win32.py", line 12, in

Re: Update Windows binaries (no pywin32 sub-problem)

As far as I remember my thoughts about pywin32 on msys after reading https://github.com/Alexpux/MINGW-packages/issues/751 shows that "it is not ready for msys". Root of a problem is in a fact that pywin32 source code contains some visual-studio-specific parts and can't be compiled with mingw.

Re: Update Windows binaries

I'm very sorry by not mentioning this earlier but pywin32 is NOT hard dependency for building meld installer, it's an *optional* dependency of cxFreeze. In the pygobject-win32 build it is only used for writing version info into exe file headers, which is useful, but not required at all. So

Re: Update Windows binaries

Thanks Vasily. I did have one more thing I tried $ wget --no-verbose https://files.pythonhosted.org/packages/d0/f7/56e35902d32299020cf9136264ca102ff0b03c0555621b469c825bc10d08/pypiwin32-220-cp36-none-win_amd64.whl && python3 -m pip install pypiwin32-220-cp36-none-win_amd64.whl

Re: Update Windows binaries

Oh, one last thing I forgot to mention is that there's currently no package for pywin32 in the MSYS2 repos either. On Sat, Apr 28, 2018 at 3:19 PM, Keegan Witt wrote: > I'm having trouble getting pywin32 installed in MSYS2. When I try to > install with pip, I get errors >

Re: Update Windows binaries

I'm having trouble getting pywin32 installed in MSYS2. When I try to install with pip, I get errors $ python3 -m pip install pypiwin32==219 Collecting pypiwin32==219 Using cached

Re: Update Windows binaries

When I do python --version, I get "Python 3.6.2" (and that's the version I see pacman downloaded). I think maybe the AIO installer is installing some stuff I don't have in pacman yet. On Tue, Mar 27, 2018 at 5:30 PM Kai Willadsen wrote: > Probably not super-helpful,

Re: Update Windows binaries

Probably not super-helpful, but I notice that you're just using `python` there, which seems to be defaulting to Python 2.7, whereas we definitely want 3.x for current Meld. Either way, I'm really happy for others to be looking at this. On 27 March 2018 at 15:16, Keegan Witt

Re: Update Windows binaries

I've started work on a pipeline for msys2 here (but it's not working yet): https://ci.appveyor.com/project/keeganwitt/meld-q7ht3. I dunno if folks are able to see settings I have so far or not, so here they are version: 3.18.1.{build} skip_non_tags: true clone_depth: 1 environment: PATH:

Re: Update Windows binaries

> On Sun, Mar 25, 2018 at 9:00 PM Keegan Witt <keeganw...@gmail.com> wrote: >> >> Sorry, I accidentally replied instead of reply all. >> >> >> -- Forwarded message - >> From: Keegan Witt <keeganw...@gmail.com> >> Date: Su

Re: Update Windows binaries

r 25, 2018 at 9:00 PM Keegan Witt <keeganw...@gmail.com> wrote: > Sorry, I accidentally replied instead of reply all. > > > -- Forwarded message - > From: Keegan Witt <keeganw...@gmail.com> > Date: Sun, Mar 25, 2018 at 8:13 PM > Subject: Re: Update