Bug #2258

Rapify problem - include file that also has a relative include define is parsed as string.

Added by kju over 5 years ago. Updated over 5 years ago.

Status:Closed Start date:06/24/2009
Priority:Normal Due date:
Assignee:kju % Done:

0%

Category:Rapify (Dos Tools)
Target version:Completed
Affected Version:

Description

namespace: x\oac\oac_core\addons\ofp_compatibility_addon

x\oac\oac_core\addons\ofp_compatibility_addon\BI\h\CfgPatches.hpp

 1 class CfgPatches
 2 {
 3     class ofp_compatibility_addon
 4     {
 5         units[] =
 6         {
 7             #include "CfgPatchesUnitsClasses.hpp" 
 8         };
 9         weapons[] =
10         {
11             #include "CfgPatchesWeaponsClasses.hpp" 
12         };
13         requiredVersion = 0.1;
14         requiredAddons[] =
15         {
16             #include "CfgPatchesRequiredAddonsClasses.hpp" 
17         };
18     };

config.cpp (in x\oac\oac_core\addons\ofp_compatibility_addon)

1 #include "BI\h\CfgPatches.hpp"

Rapify result:

 1 class CfgPatches
 2 {
 3  class ofp_compatibility_addon
 4  {
 5   units[] = {"#includeCfgPatchesUnitsClasses.hpp"};
 6   weapons[] = {"#includeCfgPatchesWeaponsClasses.hpp"};
 7   requiredVersion = 0.1;
 8   requiredAddons[] = {"#includeCfgPatchesRequiredAddonsClasses.hpp"};
 9  };

Should rapify be able to parse this correctly (not so simple) or
do I need to rework my includes to use the namespace instead of
relative includes?

Attached full source file, rapified pbo and rapified config.bin
with the prob.

config.cpp (248.5 kB) kju, 06/24/2009 19:33

ofp_compatibility_addon_rapified.zip (4 MB) kju, 06/24/2009 19:33

ofp_compatibility_addon_source.zip (4.1 MB) kju, 06/24/2009 19:33

History

Updated by mikero over 5 years ago

config cpp's (and other text files) are quite useless listed this way, especially huge ones like this

it lists quite pointless line numbers which means a select all copy paste wont work, and selecting the text is downright painfull. please supply as a zip unless the html listing can be improved

Updated by kju over 5 years ago

Hm the zip contains full source.
Also at least in this case the line numbers would match as the cfgPatches
section is the first to come.

So in other word, I don't see the problem here.

Updated by mikero over 5 years ago

  • Status changed from Assigned to Resolved
  • Target version set to Completed

fixed at 2.11 of the dll

regarding the config.cpp listing. When i click on that file, it opens a new browser window with the contents of the cpp file, together with line numbers

i cannot, under those circumstances, use a select all copy n paste to capture the file content and start working with it. Instead, i have to painfully select 'text of interest' (sections) and copy paste that with the mouse.

Updated by kju over 5 years ago

  • Status changed from Resolved to Feedback

regarding the config.cpp listing.

RMB - save as should work to get the file downloaded.


Hm wasn't able to get anywhere with rapify:

T:\pbodll>Rapify.exe -l E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file
rerun with -noisy option to see decode

T:\pbodll>Rapify.exe -ln E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file

T:\pbodll>Rapify.exe -lfn E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file

T:\pbodll>Rapify.exe -lf E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file
rerun with -noisy option to see decode

T:\pbodll>Rapify.exe -al E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file
rerun with -noisy option to see decode

T:\pbodll>Rapify.exe -aln E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file

T:\pbodll>Rapify.exe -alfn E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file

T:\pbodll>Rapify.exe -alf E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File E:\#Workspace\vehicle-dm\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file
rerun with -noisy option to see decode

Also no go with P:

T:\pbodll>Rapify.exe -l P:\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File P:\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file
rerun with -noisy option to see decode

T:\pbodll>Rapify.exe -ln P:\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File P:\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file

T:\pbodll>Rapify.exe -lfn P:\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.59, Dll Version 2.11
File P:\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file

Cannot test MakePbo atm. See #2319.

Updated by kju over 5 years ago

  • Target version deleted (Completed)

Bump. Still a problem with latest Rapify and dll. Good news is that with MakePbo it work!

T:\pbodll>Rapify.exe -l P:\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.61, Dll Version 2.18
File P:\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file
rerun with -noisy option to see decode

T:\pbodll>Rapify.exe -ln P:\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.61, Dll Version 2.18
File P:\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file

T:\pbodll>Rapify.exe -lfn P:\proper_m_dm_16_vehicle_dm.utes
Rapify.exe Version 1.61, Dll Version 2.18
File P:\proper_m_dm_16_vehicle_dm.utes Line 0 cannot open file
T:\pbodll>MakePbo.exe -A -L P:\proper_m_dm_16_vehicle_dm.utes
MakePbo.exe Version 1.61, Dll Version 2.18
Building entries..
Using $PBOPREFIX$
Creating ArmA style pbo: Prefix = proper_m_dm_16_vehicle_dm.utes
briefing.html
Creative Commons Attribution-Non-Commercial-Share Alike 3.0 Germany License.png
description.ext
init.sqf
initJIPcompatible.sqf
mission.sqm
proper_vehicle_dm\f\createAvailableVehicleSets.sqf
proper_vehicle_dm\f\findRandomLocation.sqf
proper_vehicle_dm\f\init.sqf
proper_vehicle_dm\f\listOfLaunchers.sqf
proper_vehicle_dm\f\listOfVehicles.sqf
proper_vehicle_dm\f\rearm.sqf
proper_vehicle_dm\f\rearmVehicle.sqf
proper_vehicle_dm\f\removeLockableMagazines.sqf
proper_vehicle_dm\f\removePlayable.sqf
proper_vehicle_dm\f\spawnvehicle.sqf
proper_vehicle_dm\f\vehicleSetSelection.sqf
proper_vehicle_dm\h\config.cpp
proper_vehicle_dm\h\description.hpp
proper_vehicle_dm\h\heroesOfWar.hpp
readme_dm_16_vehicle_dm.txt
.....................
Writing sha key
00F399215FFD8944463A89EA0BFDFDB6C736DE7F50

No error(s)

T:\pbodll>MakePbo.exe -A -LF P:\proper_m_dm_16_vehicle_dm.utes
MakePbo.exe Version 1.61, Dll Version 2.18
Building entries..
Using $PBOPREFIX$
Creating ArmA style pbo: Prefix = proper_m_dm_16_vehicle_dm.utes
briefing.html
Creative Commons Attribution-Non-Commercial-Share Alike 3.0 Germany License.png
description.ext
init.sqf
initJIPcompatible.sqf
mission.sqm
proper_vehicle_dm\f\createAvailableVehicleSets.sqf
proper_vehicle_dm\f\findRandomLocation.sqf
proper_vehicle_dm\f\init.sqf
proper_vehicle_dm\f\listOfLaunchers.sqf
proper_vehicle_dm\f\listOfVehicles.sqf
proper_vehicle_dm\f\rearm.sqf
proper_vehicle_dm\f\rearmVehicle.sqf
proper_vehicle_dm\f\removeLockableMagazines.sqf
proper_vehicle_dm\f\removePlayable.sqf
proper_vehicle_dm\f\spawnvehicle.sqf
proper_vehicle_dm\f\vehicleSetSelection.sqf
proper_vehicle_dm\h\config.cpp
proper_vehicle_dm\h\description.hpp
proper_vehicle_dm\h\heroesOfWar.hpp
readme_dm_16_vehicle_dm.txt
.....................
Writing sha key
00F399215FFD8944463A89EA0BFDFDB6C736DE7F50

No error(s)

T:\pbodll>MakePbo.exe -A -B P:\proper_m_dm_16_vehicle_dm.utes
MakePbo.exe Version 1.61, Dll Version 2.18
Building entries..
Using $PBOPREFIX$
Creating ArmA style pbo: Prefix = proper_m_dm_16_vehicle_dm.utes
briefing.html
Creative Commons Attribution-Non-Commercial-Share Alike 3.0 Germany License.png
description.ext
init.sqf
initJIPcompatible.sqf
mission.bin
proper_vehicle_dm\f\createAvailableVehicleSets.sqf
proper_vehicle_dm\f\findRandomLocation.sqf
proper_vehicle_dm\f\init.sqf
proper_vehicle_dm\f\listOfLaunchers.sqf
proper_vehicle_dm\f\listOfVehicles.sqf
proper_vehicle_dm\f\rearm.sqf
proper_vehicle_dm\f\rearmVehicle.sqf
proper_vehicle_dm\f\removeLockableMagazines.sqf
proper_vehicle_dm\f\removePlayable.sqf
proper_vehicle_dm\f\spawnvehicle.sqf
proper_vehicle_dm\f\vehicleSetSelection.sqf
proper_vehicle_dm\h\config.bin
readme_dm_16_vehicle_dm.txt
...................
Writing sha key
002EF4E38005307BCCBA622E0FB57DDFE5A9E95058

No error(s)

T:\pbodll>

Updated by kju over 5 years ago

  • Status changed from Feedback to Closed
  • Assignee changed from mikero to kju
  • Target version set to Completed

Again my fault..

T:\pbodll>Rapify.exe -l "p:\x\oac\oac_core\addons\oac_core\BI\h\CfgPatches.hpp" 
Rapify.exe Version 1.62, Dll Version 2.21
No error

All good.

PS: No idea why posted examples from another project in here?!

Also available in: Atom PDF