Re: [Vala] multithreading -> weird behaviour on win(msys)[SOLVED] and macOS[SOLVED]

2019-03-14 Thread Wolfgang Mauer 
Since Windows will not be the preferred environment for valaDevelop, 
that's not important at the moment.

But some other news...
Since i changed the Spawning-Process from "Process.spawn_async_with_pipes" to 
"GLib.Subprocess"as you explained before  it runs on macOS asit should!
Perfect help, thanks a lot! Wolfgang


Am 14.03.19 um 23:44 schrieb Al Thomas via vala-list:

> On Thursday, 14 March 2019, 22:13:25 GMT, Wolfgang Mauer 
 wrote: > I am now very cautious and claim that part 
of my problem is partly due

to valac (imho a valac bug)
ALL the path coming from File.get_path(), on windows should be
C:\bla\bla but the valac don't like it (proof glib-compile-resources
works with C:\bla\bla)
So the commandline to valac MUST look like this and then it works...
valac -g
--output=C:/msys64/home/Wolfgang/Projekte/vDevelop/valaDevelop/bin/valaDevelop

&-> snip <-&

C:/msys64/home/Wolfgang/Projekte/vDevelop/valaDevelop/OptionDialogs/package_options_dialog.vala

valac makes use of GLib, which provides cross-platform support for things like 
accessing files.Remember that you are operating in an MSYS2 shell. From what 
I've read MSYS2 brings aPOSIX environment to Windows and hence the forward 
slash separators.
valac shouldn't be making assumptions about the file path separators. That is 
the job of GLib.Now if you are experiencing similar problems when compiling 
with a Windows native compilerlike MSVC then there may be a bug. May be valac 
isn't using GLib as it should. May be GLibhas a bug. First, though, you need a 
better understanding of the environment you're compiling in.The could be a 
start: http://www.mingw.org/wiki/posix_path_conversion


   
___

vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] multithreading -> weird behaviour on win(msys)[SOLVED] and macOS

2019-03-14 Thread Al Thomas via vala-list 
   > On Thursday, 14 March 2019, 22:13:25 GMT, Wolfgang Mauer 
 wrote: > I am now very cautious and claim that 
part of my problem is partly due 
> to valac (imho a valac bug)

> ALL the path coming from File.get_path(), on windows should be 
> C:\bla\bla but the valac don't like it (proof glib-compile-resources 
> works with C:\bla\bla)

> So the commandline to valac MUST look like this and then it works...
> valac -g 
> --output=C:/msys64/home/Wolfgang/Projekte/vDevelop/valaDevelop/bin/valaDevelop
>  
&-> snip <-&
> C:/msys64/home/Wolfgang/Projekte/vDevelop/valaDevelop/OptionDialogs/package_options_dialog.vala
>  
valac makes use of GLib, which provides cross-platform support for things like 
accessing files.Remember that you are operating in an MSYS2 shell. From what 
I've read MSYS2 brings aPOSIX environment to Windows and hence the forward 
slash separators.
valac shouldn't be making assumptions about the file path separators. That is 
the job of GLib.Now if you are experiencing similar problems when compiling 
with a Windows native compilerlike MSVC then there may be a bug. May be valac 
isn't using GLib as it should. May be GLibhas a bug. First, though, you need a 
better understanding of the environment you're compiling in.The could be a 
start: http://www.mingw.org/wiki/posix_path_conversion


  
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] multithreading -> weird behaviour on win(msys)[SOLVED] and macOS

2019-03-14 Thread Wolfgang Mauer 

I solved part of my problem...

I am now very cautious and claim that part of my problem is partly due 
to valac (imho a valac bug)


ALL the path coming from File.get_path(), on windows should be 
C:\bla\bla but the valac don't like it (proof glib-compile-resources 
works with C:\bla\bla)


The only way to get this work is to .get_path().replace("\\", "/")(put 
the path in quotation markswill not work also).


So the commandline to valac MUST look like this and then it works...
valac -g 
--output=C:/msys64/home/Wolfgang/Projekte/vDevelop/valaDevelop/bin/valaDevelop 
--define=WINDOWS -X -DGETTEXT_PACKAGE="valaDevelop" -X -DVERSION="0..42" 
--pkg=gdk-3.0 --pkg=gee-0.8 --pkg=gio-2.0 --pkg=gio-windows-2.0 
--pkg=glib-2.0 --pkg=gmodule-2.0 --pkg=gtk+-3.0 --pkg=gtksourceview-3.0 
--pkg=json-glib-1.0 --pkg=libvala-0.42 --pkg=libxml-2.0 
--pkg=webkit2gtk-4.0 
C:/msys64/home/Wolfgang/Projekte/vDevelop/valaDevelop/OptionDialogs/package_options_dialog.vala 
C:/msys64/home/Wolfgang/Projekte/vDevelop/valaDevelop/OptionDialogs/project_options_dialog.vala 
C:/msys64/home/Wolfgang/Projekte/vDevelop/valaDevelop/OptionDialogs/rename...


Greetings
Wolfgang


Am 14.03.19 um 21:47 schrieb Wolfgang Mauer:

Hi Al,
rest assured that this should not be sarcasm! Do not think that I'm 
joking here!
And of course the source is correct, and yes i know this sounds 
impossible!!!


Hundreds of lines looks this weird, alsowith vala-compiled .c files.
To check how my command looks like I do string.joinv(" ", 
spawn_args)+"\n"

The first command still running with Process.spawn_sync and working 
glib-compile-resources 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\resources.xml 
--target=C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\resources.c 
--sourcedir=C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\resources 
--generate-source


The "Subprocess" with errors looks like this:( Tried also-X 
-DGETTEXT_PACKAGE=\"valaDevelop\" -X -DVERSION=\"0.42\" )
valac -g 
--output=C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\bin\valaDevelop 
--define=WINDOWS -X -DGETTEXT_PACKAGE="valaDevelop" -X 
-DVERSION="0..42" --pkg=gdk-3.0 --pkg=gee-0.8 --pkg=gio-2.0 
--pkg=gio-windows-2.0 --pkg=glib-2.0 --pkg=gmodule-2.0 --pkg=gtk+-3.0 
--pkg=gtksourceview-3.0 --pkg=json-glib-1.0 --pkg=libvala-0.42 
--pkg=libxml-2.0 --pkg=webkit2gtk-4.0 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionDialogs\package_options_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionDialogs\project_options_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionDialogs\rename_folder_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionDialogs\resource_create_file_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionDialogs\solution_create_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionDialogs\source_create_file_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionWidgets\IOptionWidget.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionWidgets\item_options.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionWidgets\project_options.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\OptionWidgets\solution_options.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\SearchAndReplace\replace_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\SearchAndReplace\search_and_replace.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\SearchAndReplace\search_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\SearchAndReplace\search_replace_dialog.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\SymbolFinder\reporter.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\SymbolFinder\symbol_finder.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\application_window.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\breakpoint_bookmarks.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\breakpoint_hit.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\completion_provider..vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\config.vapi 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\context_menu.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\debugger.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\debugger_symbols.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\globals.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\import_options.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\item_buildtype.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\item_type.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\main.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\main_paned.vala 
C:\msys64\home\Wolfgang\Projekte\vDevelop\valaDevelop\new_folder.vala