Skip to content

OR-Tools + SCIP -> make cc dotnet -> Windows 10, VS 2017 Pro #1188

@TornadoJo

Description

@TornadoJo

Hi all,

just my very first issue on github - so have some patience ;-)

  • building SCIP worked.
  • building OR-Tools with SCIP worked (at the end somehow....)

but I had to overcome several hurdles:
1.)

  • in the subdirectory ortools/base status_macros.h is missing
  • defining VLOG_EVERY_N_SEC e.g.:
    VLOG_EVERY_N_SEC(1, 10) << "Early abort: SCIP is in error state."; \

    and
  • defining RETURN_IF_ERROR e.g.:
    util::Status SCIPInterface::CreateSCIP() {
    RETURN_IF_ERROR(TO_STATUS(SCIPcreate(&scip_)));
    RETURN_IF_ERROR(TO_STATUS(SCIPincludeDefaultPlugins(scip_)));

    needed by "scip_interface.cc" where it includes "ortools/base/status_macros.h" - the same that is excluded in linear_solver.cc#38
    -> I couldn't find it anywhere (on github) so I created a header file defining this two things to make "make cc" work...

2.) In several first tries I added the compilerflag "c++latest" to "CFLAGS = -nologo c++latest....in "Makefile.win.mk#166" to get rid of compiler warnigns in several "make cc"-compiles --result-> several (7) linker errors at the end with added "c++latest"-flag - see attached complete log of the compile...

make.dotnet.log -> (log file represents a "make dotnet" with added status_macros.h and "c++latest" compiler flag added)

This lead to "make dotnet" to fail...

  • After creating a (compile compatible) "status_macros.h" on my own and especially removing "c++latest" again from CFLAGS "make cc" and "make dotnet" went okay so far...

Question: What would the content of status_macros.h exactly be to get a valid and complete compile? (or am I missing something else?)

Another minor detail: changed CFLAGS /D__WIN32__ to /D__WIN64__ .... hmm.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions