Re: [Mingw-w64-public] [Poll] Move to git
On 5/9/2014 21:52, JonY wrote: Hi all, You may also use the other thread for further discussion, please keep this thread for votes only. For mingw-w64 developers, state your SF ID; for the registered voters, simply reply with the same email address you registered with. [ ] Yes, move to git [ ] No, continue with SVN Polling has ended, the results are: 11 in favor of moving to git 4 opposed to moving to git The results are clear, I will allow developer write access soon and lock down SVN to read-only soon. In the mean time, here's a quick guide for SVN veterans to get into git. https://sourceforge.net/apps/trac/mingw-w64/wiki/git If you are uncomfortable with pushing, just send your patches to the mailing list, your commit ID should still be intact. You can also sign off your commit to make it more obvious. signature.asc Description: OpenPGP digital signature -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Poll] Move to git
Hi JonY, 2014-05-16 12:36 GMT+02:00 JonY jo...@users.sourceforge.net: On 5/9/2014 21:52, JonY wrote: Hi all, You may also use the other thread for further discussion, please keep this thread for votes only. For mingw-w64 developers, state your SF ID; for the registered voters, simply reply with the same email address you registered with. [ ] Yes, move to git [ ] No, continue with SVN Polling has ended, the results are: 11 in favor of moving to git 4 opposed to moving to git The results are clear, I will allow developer write access soon and lock down SVN to read-only soon. In the mean time, here's a quick guide for SVN veterans to get into git. https://sourceforge.net/apps/trac/mingw-w64/wiki/git If you are uncomfortable with pushing, just send your patches to the mailing list, your commit ID should still be intact. You can also sign off your commit to make it more obvious. the vote is clear. So we will move to git. Nevetheless there are still some pretty important points missing before we actually can do the move. First, thanks for adding the git HowTo to our Wiki. For other veteran-people I can recomment the following two links, too. https://wiki.videolan.org/Git#Configure_your_global_git_config http://wiki.winehq.org/GitWine#head-bd72d1d7bc47afa5e85f32971a8c4b3f144c12db The point, which isn't completed IMO, is that we still need to specify how our process for patch-sending, review, and actually acceptance shall work with git. As long as this isn't made clear, I still set a veto to the move from SVN to GIT. Regards, Kai -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] git migration
Hi, Git write access is now granted to developers, if you had SVN write access, you now have git write access too. SVN now read-only. For those new to git, please take a moment to read up on https://sourceforge.net/apps/trac/mingw-w64/wiki/git. It is still a stub, feel free to ask questions. Remember, if you are uncomfortable at pushing your changes, please say so. All developers are encouraged to _SIGN_ each commit if possible, for traceability and auditing purposes. See https://sourceforge.net/apps/trac/mingw-w64/wiki/git/sign to set up gnupg for signing. === Patch Review Process === The current patch review policy stays. As with SVN, patches should be sent to the public or developer list for reviews before pushing. As for pull requests from remote repositories, you should still send your patches in to the lists (use send-email or format-patch) so it can be commented on easily. Once approved, you or one of the developer may push or merge it. === On pulling upstream changes === If possible, please use git rebase instead of git merge to pull changes from the mingw-w64 git repo, so your changes are easier to review if you do plan to push back upstream. Please resend your patch after the rebase. === Git access URL === Public git://git.code.sf.net/p/mingw-w64/mingw-w64 http://git.code.sf.net/p/mingw-w64/mingw-w64 Developer write access ssh://[sourceforge ID]@git.code.sf.net/p/mingw-w64/mingw-w64 signature.asc Description: OpenPGP digital signature -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Poll] Move to git
On 5/16/2014 20:07, Kai Tietz wrote: The point, which isn't completed IMO, is that we still need to specify how our process for patch-sending, review, and actually acceptance shall work with git. As long as this isn't made clear, I still set a veto to the move from SVN to GIT. Basically, those stay the same, send patches by email for review. Once accepted, then push happens, like with SVN. signature.asc Description: OpenPGP digital signature -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [PATCH] Update OpenGL headers
On 06/05/2014 14:33, LRN wrote: On 06.05.2014 17:26, Kai Tietz wrote: 2014-05-06 15:01 GMT+02:00 LRN: Patch is of course ok. I just wanted a note on mailing-list that you've update to current (which version?). OpenGL 4.4, i think. In my RSS feed there's an entry about OpenGL 4.4 dated 2014.03.20, and one of the headers is dated 2014.03.19. And http://www.opengl.org/registry/ says 4.4 as well. If you want a more fine grained version, you can use the svn revision number from the svn repository at https://cvs.khronos.org/svn/repos/ogl/trunk/doc/registry/public/api/GL/ I think the links on the Khronos website just point to the latest version there, although they might be some manually chosen version instead. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] Getting started building examples that use std::thread
Hello, The page http://mingw-w64.sourceforge.net/download.php says: C11/C++11 Threading: C11 and C++11 have added threading support at the language level; this requires the winpthreads library which comes with the toolchains and changes little for users not relying on it. 1) Am I correct in understanding which comes with the toolchains does _not_ include win32 builds such as x86_64-4.8.2-release-win32-seh-rt_v3-rev4.7z, and applys only to posix builds? I did try to build a simple example involving std::threads using x86_64-win32-seh-rev4 -- although the compiler did not complain about #include thread it kept saying that 'thread' is not a member of 'std' 2) When I tried to use g++ from x86_64-4.8.2-release-posix-seh-rt_v3-rev4.7z (x86_64-w64-mingw32-g++.exe (x86_64-posix-seh-rev4, Built by MinGW-W64 project) 4.8.2), I got the message about missing libwinpthread-1.dll: Command used to compile (all in one line without '\'): /c/opt/mingw64/bin/x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ -static\ -libgcc \ -static\ -libstdc++ \ mt.cc -o mt.exe I do see the file /c/opt/mingw64/opt/bin/libwinpthread-1.dll -- how do I let the compiler (and the resulting executable) see this too? Thanks, --Suresh -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Getting started building examples that use std::thread
Suresh Govindachar 2014-05-17 03:45: Hello, Hi, The page http://mingw-w64.sourceforge.net/download.php says: C11/C++11 Threading: C11 and C++11 have added threading support at the language level; this requires the winpthreads library which comes with the toolchains and changes little for users not relying on it. 1) Am I correct in understanding which comes with the toolchains does _not_ include win32 builds such as x86_64-4.8.2-release-win32-seh-rt_v3-rev4.7z, and applys only to posix builds? yes, only builds using 'posix threads' supports 'C++11 thread support library': http://en.cppreference.com/w/cpp/thread 2) When I tried to use g++ from x86_64-4.8.2-release-posix-seh-rt_v3-rev4.7z (x86_64-w64-mingw32-g++.exe (x86_64-posix-seh-rev4, Built by MinGW-W64 project) 4.8.2), I got the message about missing libwinpthread-1.dll: Command used to compile (all in one line without '\'): /c/opt/mingw64/bin/x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ -static\ -libgcc \ -static\ -libstdc++ \ mt.cc -o mt.exe I do see the file /c/opt/mingw64/opt/bin/libwinpthread-1.dll -- how do I let the compiler (and the resulting executable) see this too? Try this command line: x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ -static \ mt.cc -o mt.exe -- Regards, niXman ___ Dual-target(32 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingw-w64/ ___ Another online IDE: http://liveworkspace.org/ -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Getting started building examples that use std::thread
On 5/16/2014 5:45 PM, niXman wrote: Suresh Govindachar 2014-05-17 03:45: Hello, Hi, The page http://mingw-w64.sourceforge.net/download.php says: [...] 2) When I tried to use g++ from x86_64-4.8.2-release-posix-seh-rt_v3-rev4.7z (x86_64-w64-mingw32-g++.exe (x86_64-posix-seh-rev4, Built by MinGW-W64 project) 4.8.2), I got the message about missing libwinpthread-1.dll: Command used to compile (all in one line without '\'): [fixed typo in original email involving the two -static prefixes:] /c/opt/mingw64/bin/x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ [fixed typo]-static-libgcc \ [fixed typo]-static-libstdc++ \ mt.cc -o mt.exe I do see the file /c/opt/mingw64/opt/bin/libwinpthread-1.dll -- how do I let the compiler (and the resulting executable) see this too? Try this command line: x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ -static \ mt.cc -o mt.exe Upgraded to 4.9.0 (x86_64-posix-seh-rev1, Built by MinGW-W64 project). Tried the above command and the one below -- both give the same pop-up error message from cc1plus.exe about not finding libwinpthread-1.dll: /c/opt/mingw64/bin/x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ -static \ -static-libgcc \ -static-libstdc++ \ -L/c/opt/mingw64/bin/ mt.cc -o mt.exe Perhaps I need to set some environment variable? --Suresh -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Getting started building examples that use std::thread
Suresh Govindachar sgovindac...@yahoo.com writes: Upgraded to 4.9.0 (x86_64-posix-seh-rev1, Built by MinGW-W64 project). Tried the above command and the one below -- both give the same pop-up error message from cc1plus.exe about not finding libwinpthread-1.dll: [snip] Perhaps I need to set some environment variable? Try putting the dll on a directory listed on the PATH environment variable or on the directory where your executable is. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [puzzling work-around for] Getting started building examples that use std::thread
On 5/16/2014 5:45 PM, niXman wrote: Suresh Govindachar 2014-05-17 03:45: [...] 2) When I tried to use g++ from x86_64-4.8.2-release-posix-seh-rt_v3-rev4.7z (x86_64-w64-mingw32-g++.exe (x86_64-posix-seh-rev4, Built by MinGW-W64 project) 4.8.2), I got the message about missing libwinpthread-1.dll: Command used to compile (all in one line without '\'): /c/opt/mingw64/bin/x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ [fixed typo] -static-libgcc \ [fixed typo] -static-libstdc++ \ mt.cc -o mt.exe I do see the file /c/opt/mingw64/opt/bin/libwinpthread-1.dll -- how do I let the compiler (and the resulting executable) see this too? Try this command line: x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ -static \ mt.cc -o mt.exe The above and similar commands continued to generate the same pop-up error message from cc1plus.exe about missing libwinpthread-1.dll. I also upgraded to 4.9.0 (x86_64-posix-seh-rev1, Built by MinGW-W64 project). Here's a work-around: cd /c/opt/mingw64/bin x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ -lpthread \ -static \ /c/home/suresh/mt/mt.cc -o mt.exe mv mt.exe /c/home/suresh/mt/ I can modify my Makefile to do the above 3 commands, but it would be nice to have a cleaner solution. Thanks, --Suresh -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [puzzling work-around for] Getting started building examples that use std::thread
Try this command line: x86_64-w64-mingw32-g++.exe \ -D_WIN64 \ -Wall \ -Wextra \ -Werror \ -std=c++11 \ -O3 \ -static \ mt.cc -o mt.exe I have no problem using the command line above. -- Regards, niXman ___ Dual-target(32 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingw-w64/ ___ Another online IDE: http://liveworkspace.org/ -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Getting started building examples that use std::thread
On 5/16/2014 6:52 PM, Óscar Fuentes wrote: Suresh Govindachar sgovindac...@yahoo.com writes: Upgraded to 4.9.0 (x86_64-posix-seh-rev1, Built by MinGW-W64 project). Tried the above command and the one below -- both give the same pop-up error message from cc1plus.exe about not finding libwinpthread-1.dll: [snip] Perhaps I need to set some environment variable? Try putting the dll on a directory listed on the PATH environment variable or on the directory where your executable is. Doing: export PATH=$PATH:/c/opt/mingw64/bin resolved the issue. Thanks, --Suresh -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
