suitesparse-metis-for-windows | CMake scripts for painless usage of SuiteSparse+METIS from Visual Studio and the rest of Windows/Lin | Build Tool library

 by   jlblancoc C Version: v1.7.0 License: BSD-3-Clause

kandi X-RAY | suitesparse-metis-for-windows Summary

kandi X-RAY | suitesparse-metis-for-windows Summary

suitesparse-metis-for-windows is a C library typically used in Utilities, Build Tool applications. suitesparse-metis-for-windows has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

CMake scripts for painless usage of Tim Davis' SuiteSparse (CHOLMOD,UMFPACK,AMD,LDL,SPQR,...) and METIS from Visual Studio and the rest of Windows/Linux/OSX IDEs supported by CMake. The project includes precompiled BLAS/LAPACK DLLs for easy use with Visual C++. Licensed under BSD 3-Clause License. The goal is using one single CMake code to build against SuiteSparse in standard Linux package systems (e.g. libsuitesparse-dev) and in manual compilations under Windows. Credits: Jose Luis Blanco (Universidad de Almeria); Jerome Esnault (INRIA); @NeroBurner.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              suitesparse-metis-for-windows has a low active ecosystem.
              It has 403 star(s) with 214 fork(s). There are 44 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 2 open issues and 73 have been closed. On average issues are closed in 346 days. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of suitesparse-metis-for-windows is v1.7.0

            kandi-Quality Quality

              suitesparse-metis-for-windows has 0 bugs and 0 code smells.

            kandi-Security Security

              suitesparse-metis-for-windows has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              suitesparse-metis-for-windows code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              suitesparse-metis-for-windows is licensed under the BSD-3-Clause License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              suitesparse-metis-for-windows releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.
              It has 6981 lines of code, 176 functions and 32 files.
              It has high code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of suitesparse-metis-for-windows
            Get all kandi verified functions for this library.

            suitesparse-metis-for-windows Key Features

            No Key Features are available at this moment for suitesparse-metis-for-windows.

            suitesparse-metis-for-windows Examples and Code Snippets

            No Code Snippets are available at this moment for suitesparse-metis-for-windows.

            Community Discussions

            Trending Discussions on suitesparse-metis-for-windows

            QUESTION

            Cannot compile Makefile using make command on Windows
            Asked 2021-Oct-04 at 09:30
            Problem summary

            I am trying to install an open-source parallel finite-element code called TACS and available at this github repository. To comply with the indicated prerequisites, I followed the instructions at this github repository, which allowed me to install SuiteSparse and METIS on Windows with precompiled BLAS/LAPACK DLLs. For the MPI, I installed both the Intel MPI Library and Open MPI through Cygwin. The final step should be to compile running make, however this command is not directly available in Windows 10. As a consequence, I explored the options suggested in this question, unfortunately without success. I feel at a dead end, any help will be appreciated.

            What I've tried

            Please have a look below at my attempts. I am mainly a Windows user and I don't know much of compiling programs using Makefile. My current understanding is that the Makefile that I am trying to compile is written for Linux and whatever GNU compiler for Windows I use will not work because of the different syntax needed. Please correct me if I am wrong. What I can't understand is why I get errors also when I try to compile with Ubuntu Bash for Windows 10 (last attempt of the list below).

            Visual Studio nmake

            Running the Developer Command Prompt for VS 2019 as administrator, I typed nmake -f Makefile in TACS base directory and I got Makefile.in(28) : fatal error U1001: syntax error : illegal character '{' in macro Stop.

            Chocolatey make

            Running Windows Command Prompt as administrator with C:\ProgramData\chocolatey\bin at the top of PATH environment variable, I typed make in TACS base directory and I got

            ...

            ANSWER

            Answered 2021-Oct-03 at 14:08

            I can't answer but maybe I can orient you.

            First nmake is not make. It will not work with any makefile not written specifically as an nmake makefile. And it's only available on Windows. So, best to just forget it exists.

            Second, it's important to understand how make works: rules in makefiles are a combination of targets/prerequisites, and a recipe. The recipe is not in "makefile" syntax, it's a shell script (batch file). So make works in tandem with the shell, to run commands. Which shell? On POSIX systems like GNU/Linux and MacOS it's very simple: a POSIX shell; by default /bin/sh.

            On Windows systems it's much less simple: there are a lot of options. It could be cmd.exe. It could be PowerShell. It could be a POSIX shell, that was installed by the user. Which one is chosen by default, depends on how your version of make was compiled. That's why you see different behaviors for different "ports" of make to Windows.

            So, if you look at the makefiles you are trying to use you can see they are unquestionably written specifically for a POSIX system and expect a POSIX shell and a POSIX environment. Any attempt to use a version of make that invokes cmd.exe as its default shell will fail immediately with syntax errors ("" was unexpected at this time.).

            OK, so you find a version of make that invokes a POSIX shell, and you don't get that error anymore.

            But then you have to contend with another difference: directory separators. In Windows they use backslash. In POSIX systems, they use forward slash and backslash is an escape character (so it's not just passed through the shell untouched). If you are going to use paths in a POSIX shell, you need to make sure your paths use forward slashes else the shell will remove them as escape characters. Luckily, most Windows programs accept forward slashes as well as backslashes as directory separators (but not all: for example cmd.exe built-in tools do not).

            Then you have to contend with the Windows abomination known as drive letters. This is highly problematic for make because to make, the : character is special in various places. So when make sees a line like C:/foo:C:/bar its parser will get confused, and you get errors. Some versions of make compiled for Windows enable a heuristic which tries to see if a path looks like a drive letter or not. Some just assume POSIX-style paths. They can also be a problem for the POSIX shell: many POSIX environments on Windows map drive letters to standard POSIX paths, so C:\foo is written as /c/foo or /mnt/c/foo or something else. If you are adding paths to your makefile you need to figure out what the right mapping, if any, is and use that.

            That's not even to start discussing the other differences between POSIX and Windows... there are so many.

            From what you've shown above, this project was not written with any sort of portability to Windows in mind. Given the complexity of this, that's not surprising: it takes a huge amount of work. So you have these options that I can see:

            1. Port it yourself to be Windows-compatible
            2. Try to get it working inside cygwin (cygwin is intended to be a POSIX-style environment that runs on Windows)
            3. Try to get it working in WSL
            4. Install a virtual machine using VMWare, VirtualBox, etc. running a Linux distribution and build and run it there

            Unfortunately I don't know much about the pros and cons of these approaches so I can't advise you as to the best course.

            The route I chose, long long ago, was to get rid of Windows entirely and just use GNU/Linux. But of course that won't be possible for everyone :).

            Source https://stackoverflow.com/questions/69417970

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install suitesparse-metis-for-windows

            You can download it from GitHub.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/jlblancoc/suitesparse-metis-for-windows.git

          • CLI

            gh repo clone jlblancoc/suitesparse-metis-for-windows

          • sshUrl

            git@github.com:jlblancoc/suitesparse-metis-for-windows.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link