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 in an unusual way Please contact the application's support team for more information. I'm wondering why I'm getting a Visual C++ error, if these are mingw. I think I've still got some wires crossed somewhere. On Mon, Apr 30, 2018 at 7:20 PM, Vasily Galkin <galkin...@yandex.ru> wrote: > > 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 https://gitlab.gnome.org/ > keeganwitt/meld/raw/meld-3-18-mingw/appveyor-mingw.yml > > > > The error window says > > > > cx_Freeze: Python error in main script > > Traceback (most recent call last): > > File > > C:Python34Wiblsite-packages ox Freeze initscriptsstartup > > py", line 14, in run > > File > > C:Python34Viblsite-packages ax Freezeinitscripts Console.p > > y, line 26, in run > > File bin/meld, line 29, in <module:> > > File "C:Python34libimultiprocessingicontext.py, line 148, in > > freezesupport > > File 'C:\Python34\lib\multiprocessingspawn.ру", line 74, in > > freeze support > > File .C:\Python34\lib\multiprocessing\spawn.ру", line 106, in > > spawnmain > > File .C:\Python34\lib\multiprocessing\spawn.ру", line 119, in > > main > > File .C:\Python34\lib\multiprocessingprocess.ру", line 273, in > > bootstrap > > AttributeError: "NoneType object has no attribute 'flush > > OK > > > > On Mon, Apr 30, 2018 at 6:00 PM, Vasily Galkin <galkin...@yandex.ru> > wrote: > > > >>> 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 > "error: invalid command 'bdist_msi'" for some reason. I tossed what I have > so far into https://gitlab.gnome.org/keeganwitt/meld/tree/meld-3-18-mingw. > >> > >> It looks that problem was in multiline & escaping syntax for yml > >> > >> (I haven't experience with publishing patch sets, so I created merge > request as a representation of a patchset; sorry if it is inconvenient) > >> > >> https://gitlab.gnome.org/keeganwitt/meld/merge_requests/1 > >> > >> After those modifications the bdist_msi command started (and failed for > lacking some dlls, different for 32 and 64 bit case) > >> > >> https://ci.appveyor.com/project/galkinvv/meld-ljlj2/ > build/job/ocd53kml05yobxym > >> > >> https://ci.appveyor.com/project/galkinvv/meld-ljlj2/ > build/job/tqo4ht1m1ms4k569 > >> > >>> On another topic: anybody else seeing this error when closing Meld > built with the AIO setup (it only happens when the prompt asking whether > you want to save the changes occurs)? > >> > >> Unfortunately I can't see the image - both in my mail client (web) and > in meld list archives. >
_______________________________________________ meld-list mailing list meld-list@gnome.org https://mail.gnome.org/mailman/listinfo/meld-list
