Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Windows build problem with backslashes

    Scheduled Pinned Locked Moved
    Firmware developers
    2
    3
    609
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • trayracingundefined
      trayracing
      last edited by

      I ran into linking problems on windows where the path for flash.ld was converted to backslashes by Eclipse, and then the backslashes stripped as it was handed to the linker.

      I was able to work around this by adding html quotes in the .cproject, modifying:
      -T ${workspace_loc:/${CoreName}/variants/duetNG/linker_scripts/gcc/flash.ld}
      to:
      -T"${workspace_loc:/${CoreName}/variants/duetNG/linker_scripts/gcc/flash.ld}"
      I had to enquote the map path as well.

      While having quotation marks seems quite reasonable, it seems strange to me that this isn't broken for other people as well. I am using Eclipse oxygen, as the build instructions direct. Building otherwise appears successful - should I be concerned?

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by dc42

        The behaviour of Eclipse seems to be inconsistent when paths of the form "${workspace_loc:/something}" are used. I expect you have hit another instance of that. It may be related to the length of the path to your workspace, or spaces in that path. My workspace is at C:/Eclipse/Firmware so the path is quite short and contains no spaces.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • trayracingundefined
          trayracing
          last edited by

          No spaces in my path. It is on a different drive, due to available disk space, and the path is a bit longer.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA