Kyle put the following code in his file:
-
{$IFDEF CLR}
-
{$INCLUDE ../includes/dotnet.inc}
-
{$ELSE}
-
{$INCLUDE ../includes/win32.inc}
-
{$ENDIF}
During testing, everything worked as expected, but after checking in all the files, he got an email from the build machine telling him he broke the build.
What did he do wrong?
2 Comments
I imagine Kyle might have a different search path configured for his local environment than what the build machine has.
I also wouldn’t be surprised if only one version of the compiler supports slashes to separate path elements, and the other version requires backslashes. Maybe Kyle only tested his changes on one platform.
Usually that means he forgot to check in the include files, but that seems like a simple out. I think Rob might have the right idea with the slash vs backslash or search path.
Post a Comment