No 64bits in nuget Aspose.Cells.cpp


#1

Hello,
I would like to use aspose using nuget 19.1 for C++, but the compilation failed in x64. (no librairie in package related to 64bits)
The compilation works fine in x86.
Librairies are available in the example code.
Is it possible to add x64 librairies please?

Thanks


#2

@christophe.rivier,

Thanks for your query.

Well, you may download the Aspose.Cells for C++ latest version as zipped archive from Downloads section:
https://downloads.aspose.com/cells/cpp/new-releases/aspose.cells-for-c---19.1.0/
you will find the 64-bit libraries in the folder “.\lib64” in your installation directory after extracting the zipped archive.

Hope, this helps a bit.


#3

@Amjad_Sahi mjad_Sahi
Yes, and no :slight_smile:
I already compile fine in x64 with the library you mention.
The goal with the nugget is to have a simplest portable compilation, without nugget I will be forced to create a specific trick to load library for all developers before compiling on their environment.
For industrialization, it would be more simply to have it in the nugget.


#4

@christophe.rivier,

We were able to observe the issue but we need to look into it more. We have logged the issue in our database for investigation and for a fix. Once, we will have some news for you, we will update you in this topic.

This issue has been logged as

CELLSCPP-208 - No 64bits lib support in nuget Aspose.Cells.cpp

#5

@christophe.rivier,

Could you provide details about your environment, e.g which version of Visual Studio you are using?


#6

I’m using visual Studio 2017 on windows 10


#7

@christophe.rivier,

Thanks for the details.

We will analyze your issue and get back to you with more updates.


#8

@christophe.rivier,

Just to update you, we will try to support x64 for VS2017 in Nuget in the next version.

Once the next (supported) version is published on Nuget, you will be notified here as well.


#9

@christophe.rivier,

Please try our latest version/fix: Aspose.Cells for C++ v19.3.1, it includes 64bits(x64) lib in the package archive, you may get it @ Nuget repos. here:

Let us know your feedback.


#10

Hi,

thanks it’s working fine, I have to create separate library as we already used a different boost library in our application.


#11

@christophe.rivier,

Good to know that your issue is sorted out now with the 64-bit (x64) library uploaded on Nuget repos. Feel free to contact us any time if you need further help or have some other issue or queries, we will be happy to assist you soon.


#12

Hello,

the nugget works fine in x64 release, but it didn’t compile in debug. Is it possible to add debug information ?
thanks


#13

@christophe.rivier,

Could you provide more details and sample demo application, we will check and may log a ticket for it.


#14

here is the stack of the compilation error.
AsposeExcelManagerLegacyImpl.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual __cdecl Aspose::Cells::System::String::~String(void)" (__imp_??1String@System@Cells@Aspose@@UEAA@XZ) referenced in function "public: virtual void * __cdecl Aspose::Cells::System::String::scalar deleting destructor’(unsigned int)" (??_GString@System@Cells@Aspose@@UEAAPEAXI@Z)`

AsposeExcelManagerLegacyImpl.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __cdecl Aspose::Cells::System::String::String(wchar_t const *)" (__imp_??0String@System@Cells@Aspose@@QEAA@PEB_W@Z) referenced in function "public: virtual void __cdecl XLS::CAsposeExcelManagerLegacyImpl::Open(class fermat::_tstring,class fermat::_tstring const &,class fermat::_tstring,bool)" (?Open@CAsposeExcelManagerLegacyImpl@XLS@@UEAAXV_tstring@fermat@@AEBV34@0_N@Z)

AsposeExcelManagerLegacyImpl.obj : error LNK2001: unresolved external symbol "public: virtual int __cdecl Aspose::Cells::System::Object::CompareTo(class boost::intrusive_ptr<class Aspose::Cells::System::Object>)" (?CompareTo@Object@System@Cells@Aspose@@UEAAHV?$intrusive_ptr@VObject@System@Cells@Aspose@@@boost@@@Z)

AsposeExcelManagerLegacyImpl.obj : error LNK2001: unresolved external symbol "public: virtual bool __cdecl Aspose::Cells::System::Object::Equals(class boost::intrusive_ptr<class Aspose::Cells::System::Object>)" (?Equals@Object@System@Cells@Aspose@@UEAA_NV?$intrusive_ptr@VObject@System@Cells@Aspose@@@boost@@@Z)

I tried to used the dll of the example code, but it is failing during execution on a heap memory.
All works fine in Release mode.
Regards


#15

@christophe.rivier,

As requested earlier, please share the complete sample project which can be used here to reproduce this issue. We will analyze this error message here and provide assistance at the earliest.


#16

test.zip (2.2 MB)
compilation in debug failed


#17

@christophe.rivier,
We were able to observe the issue but we need to look into it more. We have logged the issue in our database for investigation and for a fix. Once, we will have some news for you, we will update you in this topic.

This issue has been logged as

CELLSCPP-209 - x64 based program compiles fine in Release mode but fails in Debug mode

#18

@christophe.rivier,

Well, as a publishing library,we have to publish release version. Actually in release mode you can still debug in Visual Studio. Of course, we can publish a new library in Nuget to make your program compiled successfully in Debug mode. But the release library works the same as debug lib.


#19

Yes it is possible to debug in release, but with the optimized compilation in Release, some objects like list, are not accessible in Release.


#20

@christophe.rivier,

Thanks for sharing the concerns.

This makes sense. We will check if we can publish the library, so that your application should be compiled in debug mode.

Once we have any new information, we will update you.