search for: toolset

I saw an article this morning about the RH developer toolset. basically it includes a couple of packages like PHP python mysql (etc) that are later packages than that included in the released version like a 6.4 for example. So instead of php 5.3 with patches it would be php 5.4 and so on. That is great for a couple packages - but what about more up to date...

I replaced all instances of "$(Platform)" with "x64" for the x64 .props file and it still fails, so it looks like that guess was wrong as well. Regards, Eric On 9/29/14, 2:11 PM, Eric Mader wrote: > Quoting doesn't seem to make a difference. Strangely, the Win32 > toolset seems to work. (Where "work" means that clang runs and > produces a bunch of strange errors ;-) > > The only difference I see between the two .props files is that one > passes "-m86" to the compiler and the other one passes "-m64". > > They both ref...

Hi Hans, I think installer.bat found my visual Studio installation because it installed the Win32 toolsets but not the x64 ones. (It took me a while to work this out ;-) I installed the x64 toolsets by hand and they seem to work. I think the installer ran as administrator. I explicitly ran it that way again (asking it to uninstall first) just to be sure. It didn't seem to make any difference....

...; wrote: > I changed tooset-vs2013.props to this: > > <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" > <http://schemas.microsoft.com/developer/msbuild/2003>> > <Import > Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props" > Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props')"/> > <Import > Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Tool...

Open the file toolset-vs2013.props and you'll understand what's happening and where the path is set. It tries to fetch the LLVM installation path from the Windows registry. Just fix this (maybe editing your registry or editing the .props file, whatever suits you best). On Mon, Sep 29, 2014 at 5:33 PM, Eric Made...

...; > Also, there are a few updates still missing: dhcp-4.1.1-61.P1.el6_10, > qemu-kvm-0.12.1.2-2.506.el6_10.1 and kernel-2.6.32-754.2.1.el6. > They will all be there once all the tool sets for firefox are done building .. that is what the builders are all doing right now .. el6 and el7 devtoolset-7, llvm-toolset-7, rust-toolset-7 and all the deps / prereqs, bootstraps, etc. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermai...

...; > > > > > > OK guys .. Firefox 60 is going to take some time .. likely more for > > > > > CentOS-6 than CentOS-7. > > > > > They both (C6 and C7 versions) require many non OS tools to build. > > > > > For CentOS-7 .. we need the rust-toolset, llvm-toolset, and > > > > > devtoolset-7, to get the firefox to build. > > > > > > > > > > > > > > > > <snip> > > > > > > > > My current issue building the latest firefox is the required rust > >...

...>>>>> OK guys .. Firefox 60 is going to take some time .. likely more for >>>>>>> CentOS-6 than CentOS-7. >>>>>>> They both (C6 and C7 versions) require many non OS tools to build. >>>>>>> For CentOS-7 .. we need the rust-toolset, llvm-toolset, and >>>>>>> devtoolset-7, to get the firefox to build. >>>>>> >>>>>> >>>>>> >>>>>> <snip> >>>>>> >>>>>> My current issue building the latest firefox...

...ns, Answers inline below. Regards, Eric On 9/30/14, 8:05 AM, Hans Wennborg wrote: > On Mon, Sep 29, 2014 at 7:56 PM, Eric Mader <emader at gmx.us> wrote: >> Hi Hans, >> >> I think installer.bat found my visual Studio installation because it >> installed the Win32 toolsets but not the x64 ones. (It took me a while to >> work this out ;-) I installed the x64 toolsets by hand and they seem to >> work. > Hmm, that's interesting. Is your x64 toolset path different besides > substituting the Win32 dir with x64? They're the same except for Win32...

...e: > On 07/03/2018 09:04 AM, Sean wrote: > > > <snip> > OK guys .. Firefox 60 is going to take some time .. likely more for > CentOS-6 than CentOS-7. > > They both (C6 and C7 versions) require many non OS tools to build. > > For CentOS-7 .. we need the rust-toolset, llvm-toolset, and > devtoolset-7, to get the firefox to build. > > <snip> My current issue building the latest firefox is the required rust version. In the [sclo-rh] section of the epel-7 mock config I change line: includepkgs=devtoolset* to includepkgs=devtoolset* llvm-tool...

I’m trying to install LLVM-3.6.0-r218288-win32.exe on Windows 7 Ultimate x64. The install doesn’t complain, but the toolset doesn’t show up in either Visual Studio 2013 or Visual Studio 2010. Also I selected the choices to add LLVM to the path for every user and put an LLVM icon on the desktop. Neither of this happened. Can anyone tell me how to get this to work? Regards, Eric Mader

Hi all, I could find the 1.1 and 2 repos gently provided by Tru Huynh, but quid of a v3 of the toolset? I've just found that Qt 5.4 requires what's shipped in this v3 (gcc 4.9.1, binutils 2.24) and would prefer installing those from a repo. If not, the sources will rule. Any hint? Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not av...

...t;> >> <snip> >> >>> OK guys .. Firefox 60 is going to take some time .. likely more for >>> CentOS-6 than CentOS-7. >> >>> They both (C6 and C7 versions) require many non OS tools to build. >> >>> For CentOS-7 .. we need the rust-toolset, llvm-toolset, and >>> devtoolset-7, to get the firefox to build. >> >> >> >> <snip> >> >> My current issue building the latest firefox is the required rust version. >> >> In the [sclo-rh] section of the epel-7 mock config I change line...

...;m not sure about the Windows installer, but if you build and install > LLVM for Windows from the source code, you should be able to go to the > installation folder, find a subfolder named "tools/msbuild" and run > the "install.bat" script. This should make your LLVM toolset appear in VS. > > On Mon, Sep 29, 2014 at 2:52 PM, Eric Mader <emader at gmx.us > <mailto:emader at gmx.us>> wrote: > > I’m trying to install LLVM-3.6.0-r218288-win32.exe on Windows 7 > Ultimate x64. The install doesn’t complain, but the toolset > doesn...

...-) Please help. Greetings and thanks for all. Ernesto ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter

I am pleased to announce the immediate availability of Developer Toolset 3 on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-...

Hi, May be it's not clear to everyone.. so this's just a quick notice to everyone. Don't use CentOS 7 as a developer workstation since currently there is not included any developer IDE. As eclipse was pulled out from the main distro and put into Red Hat Developer Toolset (which is imho a good idea not to use a 7 years old IDE). But Red Hat Developer Toolset is still not supported on rhel7 this means currently you have to install eclipse and all other packages from RHDT. Anyway RH said it will be supported... Regards. -- Levente &q...

...of > customization of automake itself, it just can't grok the fact that there > might be multiple ways to compile a c/c++ program producing different > results and requiring different tools. Boost.Build supports this very good. In particular, on my project on work I can run: bjam toolset=gcc bjam toolset=nm bjam toolset=nmm and the first will do a regular build, the third will compile for some embedded processor, and the third will pass the sources via some annotation tool and produce an annotated x86 binary. Besides, "toolset=gcc" can become "toolset=msvc&...

I am pleased to announce the immediate availability of Developer Toolset 4 on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-...

I am pleased to announce the immediate availability of Developer Toolset 3 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install devto...