As far as I can tell, the Windows command line build relies on a file
(cfg.h) in each of the mpn assembler directories. This file holds a list of
the assembler files in the directory
But there is a potential problem here because these cfg.h files are built
only when the Visual Studio build for each architecture is generated. In
consequence a command line build for an architecture will only work after
the Visual Studio build is generated for this architecture. This is a
potential problem since it will be faar from obvious for those who use the
command line build that they have to run the Visual Studio build generator
for the architecture in question before they run the command line build.
There are several ways of handling this. The first is to document the need
to run the Visual Studio build generator before running a Windows command
line build. The second is to modify the Visual Studio build generator so
that it can be called from the command line build process and hence
generate the needed cfg.h file. The third is to generate and add all the
needed cfg.h files to the MPIR repository and MPIR distributions.
The first of these is simple but unlikely to work well as many users don't
pay much attention to the documentation. The third is painful as it will be
an ongoing maintenance nightmare. Which leaves the second option, one
which will require quite a bit of work by me and by Jason or Case. This
will also mean that the command line build will end up with a Python
dependency (assuming that we can run Python from the command line build
script).
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mpir-devel/-/7CV3fPZGk5QJ.
To post to this group, send email to mpir-devel@googlegroups.com.
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
