Add ifdef for macro compatibility

example-project/EZPlatformer/source/import.hx

@@ -1,3 +1,5 @@
+#if !macro
 import FmodConstants.FmodSFX;
 import FmodConstants.FmodSongs;
-import haxefmod.FmodManager;
+import haxefmod.FmodManager;
+#end

fmod-scripts/README.md

@@ -4,7 +4,7 @@ This script utilizes a very cool feature in FMOD Studio to give your code access
 
 It does this by placing an `FmodConstants.hx` file next to your main `.hx` file which you can then import into your project.
 
-If you are using vscode, its autocomplete can be triggered by typing in "FmodSongs." or "FmodSFX." 
+If you are using vscode, its autocomplete can be triggered by typing in "FmodSongs." or "FmodSFX."
 
 ![Haxe Constants Demo](https://raw.githubusercontent.com/Tanz0rz/haxe-fmod/34baff733a24e4301b6b8457066cae870fb22570/HaxeConstants.gif)
 
@@ -23,17 +23,23 @@ To avoid having to import three classes in every file of your game code, you can
 
 `import.hx`:
 ```haxe
+// Only use imports when not in the macro context.
+// The FMOD files use build macros and will throw errors if imported within the macro context.
+#if !macro
+
 // Fmod helper library
 import haxefmod.FmodManager;
 // Static class containing all sound effect names
 import FmodConstants.FmodSFX;
 // Static class containing all song names
 import FmodConstants.FmodSongs;
+
+#end
 ```
 
 ## Installing the script:
 - Place the ExportHaxeConstants.js file in your FMOD Studio's "scripts" folder. This folder will be found wherever you installed FMOD Studio on your computer.
-- In FMOD Studio, click the Scripts dropdown at the top and select "Reload". 
+- In FMOD Studio, click the Scripts dropdown at the top and select "Reload".
 - Click on the Scripts dropdown again and you will see an "Export Haxe Constants" option now available.
 - When prompted, select the directory in your Haxe project that contains your `Main.hx` file (this is usually the `/source` directory).