Or you can use MinGW, it’s not tricky, you don’t need to change any PETSc code, and you can ship .exe for either x86_64 (mingw-w64-x86_64-gcc) or ARM (mingw-w64-clang-aarch64-clang, without MPI).
Thanks, Pierre > On 7 Nov 2022, at 1:38 PM, hamid badi <[email protected]> wrote: > > You can try gcc/clang cross-compilers, it's a little but tricky, i had to > change some petsc codes but it works fine. > > Le lun. 7 nov. 2022 à 13:30, Matthew Knepley <[email protected] > <mailto:[email protected]>> a écrit : >> On Mon, Nov 7, 2022 at 7:11 AM Mohammad Ali Yaqteen <[email protected] >> <mailto:[email protected]>> wrote: >>> Once I finish writing the code, the .exe file will not change. Can I make >>> an .exe file using WSL2 and VScode? >>> >> >> If you build in WSL2, it will link to system libraries. You would probably >> need to run in WSL2 after that. If you are planning >> on running on native Windows, you likely need to build there. >> >> Thanks, >> >> Matt >> >>> Thanks, >>> >>> Ali >>> >>> >>> >>> From: Matthew Knepley <[email protected] <mailto:[email protected]>> >>> Sent: Monday, November 7, 2022 7:13 PM >>> To: Mohammad Ali Yaqteen <[email protected] <mailto:[email protected]>> >>> Cc: petsc-users <[email protected] <mailto:[email protected]>> >>> Subject: Re: [petsc-users] PETSc Windows Installation >>> >>> >>> >>> On Mon, Nov 7, 2022 at 12:21 AM Mohammad Ali Yaqteen <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> I have written backend code for a software company. If WSL2 and >>> VSCode(Linux) can be called through a command line and executed at the >>> backend, then it will be great. But if I have to install WSL2 and other >>> required things on every other PC that will run that software, then I think >>> I will be at a disadvantage. What do you suggest? >>> >>> >>> >>> As long as you do not change the architecture and the compiler libraries >>> are available, you can run the executable. >>> >>> >>> >>> Thanks, >>> >>> >>> >>> Matt >>> >>> >>> >>> Thank you >>> Ali >>> >>> -----Original Message----- >>> From: Satish Balay <[email protected] <mailto:[email protected]>> >>> Sent: Monday, November 7, 2022 12:00 AM >>> To: Matthew Knepley <[email protected] <mailto:[email protected]>> >>> Cc: Mohammad Ali Yaqteen <[email protected] >>> <mailto:[email protected]>>; [email protected] >>> <mailto:[email protected]> >>> Subject: Re: [petsc-users] PETSc Windows Installation >>> >>> Likely the compilers are not setup correctly as per instructions. >>> >>> https://petsc.org/release/install/windows/#installation-with-microsoft-intel-windows-compilers >>> >>> And if you do not have a specific windows need - and only need IDE - >>> perhaps a WSL2 (aka linux) install with VSCode(linux) might be the way to >>> go. >>> >>> Satish >>> >>> On Sun, 6 Nov 2022, Matthew Knepley wrote: >>> >>> > We need to see configure.log to see what is going on. Can you send it? >>> > >>> > Thanks, >>> > >>> > Matt >>> > >>> > On Sun, Nov 6, 2022 at 4:29 AM Mohammad Ali Yaqteen >>> > <[email protected] <mailto:[email protected]>> >>> > wrote: >>> > >>> > > Dear Sir/Madam, >>> > > >>> > > >>> > > >>> > > I am installing PETSc on windows but it keeps giving me unexpected >>> > > errors. >>> > > I want to use it on MS Visual Studio or Codeblocks. When I use the >>> > > command on your webpage (./configure --with-cc='win32fe cl' >>> > > --with-fc='win32fe ifort' --with-cxx='win32fe cl' --with-mpi=0 >>> > > --download-fblaslapack), I get the following error message: >>> > > >>> > > >>> > > >>> > > $ ./configure --with-cc='win32fe cl' --with-fc='win32fe ifort' >>> > > --with-cxx='win32fe cl' --with-mpi=0 --download-fblaslapack >>> > > >>> > > >>> > > ==================================================================== >>> > > ========================= >>> > > >>> > > Configuring PETSc to compile on your system >>> > > >>> > > >>> > > ==================================================================== >>> > > ========================= >>> > > >>> > > TESTING: checkCCompiler from >>> > > config.setCompilers(config/BuildSystem/config/setCompilers.py:1341)* >>> > > ******************************************************************** >>> > > ********** >>> > > >>> > > UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log >>> > > for >>> > > details): >>> > > >>> > > >>> > > -------------------------------------------------------------------- >>> > > ----------- >>> > > >>> > > C compiler you provided with -with-cc=win32fe cl cannot be found or >>> > > does not work. >>> > > >>> > > Cannot compile/link C with >>> > > /home/SEJONG/petsc-3.18.1/lib/petsc/bin/win32fe/win32fe cl. >>> > > >>> > > >>> > > >>> > > Kindly look into this problem! Your prompt response will highly be >>> > > appreciated >>> > > >>> > > >>> > > >>> > > Thank you >>> > > >>> > > Ali >>> > > >>> > >>> > >>> > >>> >>> >>> >>> >>> >>> -- >>> >>> What most experimenters take for granted before they begin their >>> experiments is infinitely more interesting than any results to which their >>> experiments lead. >>> -- Norbert Wiener >>> >>> >>> >>> https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/> >> >> -- >> What most experimenters take for granted before they begin their experiments >> is infinitely more interesting than any results to which their experiments >> lead. >> -- Norbert Wiener >> >> https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
