1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Build system question |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Sun, 10 Sep 2023 16:57:57 +0000 |
I have a questions about the build system on Windows when directory names contain space characters. I have a vendor library in “C:\BitFlow SDK 6.5”. It contains Include/ and Lib64/ directories. I want to build my application using the files in those directories. My application Makefile contains lines like: USR_INCLUDES += -I$(BITFLOW_SDK_INCLUDE) PROD_LIBS_WIN32 += BFGTLUtil USR_LDFLAGS_WIN32 += /LIBPATH:$(BITFLOW_SDK_LIB) I created CONFIG_SITE.windows-x64-static.Common with these lines: BITFLOW_SDK_INCLUDE = “C:/BitFlow SDK 6.5/Include” BITFLOW_SDK_LIB = “C:/BitFlow SDK 6.5/Lib64” That does not work because of the embedded spaces in the folder name. I also tried this: BITFLOW_SDK_INCLUDE = “C:/BitFlow\ SDK\ 6.5/Include” BITFLOW_SDK_LIB = “C:/BitFlow\ SDK\ 6.5/Lib64” Is there a way to make it work when the folder name contains space characters? I ended up renaming the vendor directory to replace spaces with underscores. I also had to remove the quotation marks in the CONFIG_SITE file. BITFLOW_SDK_INCLUDE = C:/BitFlow_SDK_6.5/Include BITFLOW_SDK_LIB = C:/BitFlow_SDK_6.5/Lib64 Thanks, Mark |