Re: Is Visual Studio Express 2017 Free For Commercial Use

5 views
Skip to first unread message
Message has been deleted

Christopher Caldera

unread,
Jul 16, 2024, 10:54:40 PM7/16/24
to breathpugseled

Is anyone cross compiling on Linux for Windows and is willing to share some info? I found some tutorials on the net (using "mxe"), but I'm lost. I am probably missing basic Windows knowledge. I looked at the thread in this forum about setting up the compiling environment on all three OSses, but that seems qmake centric and based on commercial windows visual studio software. I am not handy with GUIs, I need a TUI, which explains my lack of windows experience

Thanks! I had actually been looking at your datareftool setup before for the cmake stuff :-)

I guess I'll need to look at visual studio... how does that work with cmake? Can de cmake makefile be used with visual studio? or would one just use the compiler bit from the windows command line (if that is possible...)?

-peter

is visual studio express 2017 free for commercial use


Descargar https://tiurll.com/2yOQNL



Thanks! I had actually been looking at your datareftool setup before for the cmake stuff :-)

I guess I'll need to look at visual studio... how does that work with cmake? Can de cmake makefile be used with visual studio? or would one just use the compiler bit from the windows command line (if that is possible...)?

If you use the -Wall flag in your CMakeLists.txt, the Visual Studio project will take that quite literally and turn on all possible errors. I worked on a project recently with 750,000 warnings and 0 errors in Visual Studio for this reason.

Now I'm stuck on errors like "cannot specify explicit initialiser for arrays", etc. The compilers on Mac and Linux don't give errors here so it appears I do have to make changes in my code for Windows. And we haven't even reached the linking stage...

Now I'm stuck on errors like "cannot specify explicit initialiser for arrays", etc. The compilers on Mac and Linux don't give errors hereB) so it appears I do have to make changes in my code for Windows. And we haven't even reached the linking stage...

I managed to fix the compiler errors, and am now at the linking stage. I was meaning to ask already about 32 and 64 bit, but the errors are apparently way ahead of me. "fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'". (Probably yet another cmake configuration error?)

I made a VirtualBox on my Mac (I gave up on cross compiling on Linux) with a Windows 7 where I installed cmake and Visual Studio Express 2012, and I have succesfully built a 32 and 64 bit win.xpl plugin, as far as I can tell. (success in this case is X-Plane starting up and finding plugin in the log).

For instance on archlinux you need the mingw-w64-gcc package and mingw-w64-cmake. The latter provides a toolchain file for cmake, so that in order to cross-compile you can simply invoke cmake with:

I work for a commercial engineering and science company. Our company policies require our software to be routinely and automatically updated. This morning, Visual Studio 2022 was updated to version 17.8.3. After that, the Fortran and C++ Windows MDI application that I have been working on stopped compiling with different linking errors. Initially, the error was "error LNK1104: cannot open file 'ifconsol.lib' ", which I found this KN article addressing. However, the instructions in the article did not work. I have the 2024 version of the Intel OneAPI and HPC installed. But the macro from the article does not resolve to the correct location:

C:\Program Files (x86)\Intel\oneAPI\compiler\2024.0\lib32. I manually added this path and my application was able to compile again. Is there a way to correct the MACRO $(IFORT_COMPILER24)? I have other developers I am working with and we do not all necessarily have the Intel OneAPI installed in the same location, so I would prefer to use the MACRO rather than having to have each person adjust the project properties everytime someone else needs to compile the application.

This is fascinating. I can confirm that the environment variable IFORT_COMPILER24 points to a non-existent folder. That path did exist in the 2023.2.0 version. Evidently the directory structure got rearranged - AGAIN - but the environment variable did not keep up.

But when I look at the compiler settings in VS, I don't see IFORT_COMPILER24 used at all - instead it references $(IFortInstallDir) which is set correctly. As you are using a mixed-language application, you very likely added a reference to IFORT_COMPILER24 so that MSVC could locate the Fortran libraries.

You could change the value of IFORT_COMPILER24 at the system level, but a new install of Intel Fortran might overwrite it. I do wish that Intel would come up with a more robust scheme for other languages and build scripts to find the compiler and its libraries/includes. This has been a pain point for many years.

The Unified Directory Layout is implemented in 2024.0. If you have multiple toolkit versions installed, the Unified layout ensures that your development environment contains the correct component versions for each installed version of the toolkit. The directory layout used before 2024.0, the Component Directory Layout, is still supported on new and existing installations.

For detailed information about the Unified layout, including how to initialize the environment and advantages with the Unified layout, refer to Use the setvars and oneapi-vars Scripts with Linux and Use the setvars and oneapi-vars Scripts with Windows.

The page Configuring Visual Studio for Mixed-Language Applications is related to this. It hasn't been updated for directory layout changes for the 2024.0 release. It was still useful as it gave me the clues I needed to update stuff.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

To do this you need to locate the "applicationhost.config" file. After VS2015 it's located in [solutiondir]\.vs\config\applicationhost.config. (If you are working at a museum and use a visual studio version before 2015, you can find the file in MyDocuments/IISExpress/config, but you should also remember to first put coal in your steam engine to power on your computer).

In this file, you'll want to find the path to site/bindings and add a binding like this:


Where '52494' would be the port number. Note that I'm using HTTP, as HTTPS would require you to setup a local certificate for it. The IISExpress default certificate only works for localhost.

Hone your skills, explore new artistic outlets, or transfer to a four-year program at a university with the Central Texas College Visual Arts program Associate of Arts degree in studio art. The Visual Art faculty will help you to develop new skills and to express your creativity. Upon obtaining your degree you will possess skills highly appreciated in many industries and have the tools necessary to turn your passion into a career. Or, if you plan to continue your art education, the Visual Art faculty will ensure that you have strong foundation skills and a sharp portfolio.

Art majors will discover instruction in two-dimensional and three-dimensional studio courses, design, drawing, life drawing, painting, photography both traditional darkroom and digital processes, design communications with a focus on Adobe Photoshop and Illustrator programs, ceramics and art metals/jewelry.

d3342ee215
Reply all
Reply to author
Forward
0 new messages