Jump to content

Visual studio 2022 compiling issue


Recommended Posts

Hello guys , 

 

im trying to compile my source and im having these errors .. 

at my friend its compiling well , i have all the needed extensions and everything

can someone please explain me more about the problem ? 

 

https://metin2.download/picture/zt9pLHSE3ZFd8I8Ut12Pxa4wgum6K8Cz/.png

 

https://metin2.download/picture/8VoGs3EZ99evfE5QYiRYRtVX00Z8gd0F/.png

 

https://metin2.download/picture/5UXv6T5loPI8NqNjxIZQ9fAbUiNwzFKE/.png

 

Thanks

 

 

Edited by Metin2 Dev
Core X - External 2 Internal
Link to comment
Share on other sites

  • Replies 6
  • Created
  • Last Reply

Top Posters In This Topic

This include affected my binary , so its not the right solution .. 

 

again i have a bad path while building my srcs , 

 

VS 2022 in use . 

 

https://metin2.download/picture/iGS4Susdr23u23900538A0kNbN2ARyH4/.png

 


Error    MSB3073    The command "cd C:\Users\Ziad-\OneDrive\Desktop\Altyapı\Binary\Client\CRootLib\\Workplace\
call 2.bat
call 3.bat

I dont know if its related to this code

if someone can help please thanks 

 

    <PreBuildEvent>
      <Command>cd $(ProjectDir)\Workplace\
call 2.bat
call 3.bat
</Command>
      <Message>cythonizing root</Message>
    </PreBuildEvent>
  </ItemDefinitionGroup>
  <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
    <ClCompile>
      <WarningLevel>Level3</WarningLevel>
      <PrecompiledHeader>
      </PrecompiledHeader>
      <Optimization>MaxSpeed</Optimization>
      <FunctionLevelLinking>true</FunctionLevelLinking>
      <IntrinsicFunctions>true</IntrinsicFunctions>
      <PreprocessorDefinitions>_CRT_SECURE_NO_WARNINGS;WIN32;NDEBUG;_LIB;%(PreprocessorDefinitions)</PreprocessorDefinitions>
      <AdditionalIncludeDirectories>..\..\Extern\include\Python-2.7;..\..\Extern\include</AdditionalIncludeDirectories>
      <FavorSizeOrSpeed>Speed</FavorSizeOrSpeed>
      <CompileAs>CompileAsC</CompileAs>
      <MultiProcessorCompilation>true</MultiProcessorCompilation>
      <RuntimeLibrary>MultiThreaded</RuntimeLibrary>
      <OmitFramePointers>true</OmitFramePointers>
      <InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
      <WholeProgramOptimization>false</WholeProgramOptimization>
      <BrowseInformation>true</BrowseInformation>
    </ClCompile>
    <Link>
      <SubSystem>Windows</SubSystem>
      <GenerateDebugInformation>true</GenerateDebugInformation>
      <EnableCOMDATFolding>true</EnableCOMDATFolding>
      <OptimizeReferences>true</OptimizeReferences>
    </Link>
    <PreBuildEvent>
      <Message>cythonizing root</Message>
      <Command>cd $(ProjectDir)\Workplace\
call 2.bat
call 3.bat
</Command>

Edited by Metin2 Dev
Core X - External 2 Internal
Link to comment
Share on other sites

  • Contributor
Spoiler

  

13 hours ago, ziad said:

This include affected my binary , so its not the right solution .. 

 

again i have a bad path while building my srcs , 

 

VS 2022 in use . 

 

https://metin2.download/picture/iGS4Susdr23u23900538A0kNbN2ARyH4/.png

 


Error    MSB3073    The command "cd C:\Users\Ziad-\OneDrive\Desktop\Altyapı\Binary\Client\CRootLib\\Workplace\
call 2.bat
call 3.bat

I dont know if its related to this code

if someone can help please thanks 

 

    <PreBuildEvent>
      <Command>cd $(ProjectDir)\Workplace\
call 2.bat
call 3.bat
</Command>
      <Message>cythonizing root</Message>
    </PreBuildEvent>
  </ItemDefinitionGroup>
  <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
    <ClCompile>
      <WarningLevel>Level3</WarningLevel>
      <PrecompiledHeader>
      </PrecompiledHeader>
      <Optimization>MaxSpeed</Optimization>
      <FunctionLevelLinking>true</FunctionLevelLinking>
      <IntrinsicFunctions>true</IntrinsicFunctions>
      <PreprocessorDefinitions>_CRT_SECURE_NO_WARNINGS;WIN32;NDEBUG;_LIB;%(PreprocessorDefinitions)</PreprocessorDefinitions>
      <AdditionalIncludeDirectories>..\..\Extern\include\Python-2.7;..\..\Extern\include</AdditionalIncludeDirectories>
      <FavorSizeOrSpeed>Speed</FavorSizeOrSpeed>
      <CompileAs>CompileAsC</CompileAs>
      <MultiProcessorCompilation>true</MultiProcessorCompilation>
      <RuntimeLibrary>MultiThreaded</RuntimeLibrary>
      <OmitFramePointers>true</OmitFramePointers>
      <InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
      <WholeProgramOptimization>false</WholeProgramOptimization>
      <BrowseInformation>true</BrowseInformation>
    </ClCompile>
    <Link>
      <SubSystem>Windows</SubSystem>
      <GenerateDebugInformation>true</GenerateDebugInformation>
      <EnableCOMDATFolding>true</EnableCOMDATFolding>
      <OptimizeReferences>true</OptimizeReferences>
    </Link>
    <PreBuildEvent>
      <Message>cythonizing root</Message>
      <Command>cd $(ProjectDir)\Workplace\
call 2.bat
call 3.bat
</Command>

 

 

call 2.bat
call 3.bat

I see they are used to cythonize the root. If you don't have these, remove them from the build events.

If you have them, update your paths.

Also, try common sense, it usually works(like with your first problem, one simple google search would've taken you to this page https://en.cppreference.com/w/cpp/memory/shared_ptr, which clearly says shared_ptr is defined in the <memory> header)

 

Good luck

Edited by Metin2 Dev
Core X - External 2 Internal
Link to comment
Share on other sites

@ Amun the problem is that the guy i bought the source from is building normaly in front of me in anydesk , and archiving the file and sending it ( the same as he built succesfully ) 

 

hes not adding <include> memory and nthg and its working like a charm .. 

mine is using a cd command .. idk why but ye .. 

 

Btw thank you for your time ! ❤️

 

Edited by ziad
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.