Skip to content

Native build failed with CLI #124

Closed
Closed

Description

@malekatwiz

Trying to build on Windows using CLI first, ran build.cmd in root folder
build started and was looking fine, until it started building native components.

Error Message

machinelearning-master\src\Native\build.proj(47,5): error MSB3073
machinelearning-master\src\Native\build.cmd Debug x64" exited with code 255.

Build FAILED.

Time Elapsed 00:00:02.03
Command execution failed with exit code 1.

any ideas?

Activity

  1. veikkoeeva commented on May 11, 2018

    @veikkoeeva
    Contributor

    @malek8 Do you have the native toolchain installed? Either via VS 2017 or perhaps http://landinghub.visualstudio.com/visual-cpp-build-tools ? Other one I can imagine of is CMake (the tools do not use the private one VS C++ tools installs).

  2. malekatwiz commented on May 12, 2018

    @malekatwiz
    Author

    @veikkoeeva I have native installed, CMake and C++ build tools.
    I double checked the instructions again, from workloads and individual components. looks like i have all required components installed.. pulling my hair here

  3. veikkoeeva commented on May 12, 2018

    @veikkoeeva
    Contributor

    @malek8 Indeed, those error message do not tell much. Can you increase build logging to maximum? The setting is something like

    Tools -> Options -> Build and Run Change -> MsBuild project build output verbosity | "Diagnostic".

    A hunch is that something isn't found on the path, but I haven't taken a look at the build files. Maybe adding quotes around path name or some other measure would help. Additional option could be to switch to the new binary logging (probably should be done in any case) and even ship the binary logs here for someone else to view on too.

    As an aside, the MSBuild could check if the toolchain has run so opening VS would be enough, maybe something to do a PR later. :)

  4. malekatwiz commented on May 12, 2018

    @malekatwiz
    Author

    Mystery solved!
    I had a wrong entry in environment path prior to CMake entry, and it wasn't leading to a valid directory. @veikkoeeva thanks for the insight

  5. veikkoeeva commented on May 12, 2018

    @veikkoeeva
    Contributor

    Further improvement idea: check if the paths used do exist and have the tools needed and print approriate error messages.

  6. ghost locked as resolved and limited conversation to collaborators on Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions