URL:
  <http://gna.org/bugs/?10208>

                 Summary: Slight fix to add full paths in resource_lexer.l &
strres_lexer.l
                 Project: Warzone Resurrection Project
            Submitted by: None
            Submitted on: Saturday 10/27/2007 at 19:00 CEST
                Category: Build system
                Severity: 1 - Trivial
                Priority: 5 - Normal
                  Status: None
             Assigned to: None
        Originator Email: [EMAIL PROTECTED]
             Open/Closed: Open
         Discussion Lock: Any
                 Release: svn/trunk
        Operating System: Microsoft Windows
         Planned Release: None

    _______________________________________________________

Details:

If you don't have full paths, then MSVC build errors out, since "frame.h" is
not in the path of __DEVPKG__\include || $(SolutionDir)\.. ||
$(SolutionDir).

So to keep conformity with the other #include files pattern, here is a fix.


Index: lib/framework/resource_lexer.l
===================================================================
--- lib/framework/resource_lexer.l      (revision 2640)
+++ lib/framework/resource_lexer.l      (working copy)
@@ -24,7 +24,7 @@
  * Lex file for parsing res files
  */
 
-#include "frame.h"
+#include "lib/framework/frame.h"
 
 #include <stdio.h>
 
Index: lib/framework/strres_lexer.l
===================================================================
--- lib/framework/strres_lexer.l        (revision 2640)
+++ lib/framework/strres_lexer.l        (working copy)
@@ -24,7 +24,7 @@
  * Lex file for parsing string resource files
  */
 
-#include "frame.h"
+#include "lib/framework/frame.h"
 
 #include <stdio.h>
 




    _______________________________________________________

Reply to this item at:

  <http://gna.org/bugs/?10208>

_______________________________________________
  Message sent via/by Gna!
  http://gna.org/


_______________________________________________
Warzone-dev mailing list
[email protected]
https://mail.gna.org/listinfo/warzone-dev

Reply via email to