Skip to content

[Suggestion] Analyse & decide on src/megacli.* #112

Description

@Olf0

I discovered that the files src/megacli.cpp and src/megacli.h are not referenced in their corresponding sections (categories SOURCES and HEADERS) of filecase.pro, see PR #105 for testing which unreferenced files are actually usable.
Then I documented these (and other) findings "inline" in filecase.pro via PR #107.

Trying to chase down the origin of "MegaCLI", I found https://github.com/meganz/sdk

O.K, this is apparently a well maintained repository documenting multiple ways to interact with the Mega.nz "secure cloud storage provider", among them the MegaCLI-tool whose source code is also hosted in this repository.

Ultimately I "compile-tested" src/megacli.* by referencing them in their corresponding sections (categories SOURCES and HEADERS) of filecase.pro via PR #109: The result shows, that it does not compile.

But this issue should be well addressable by utilising the content of aforementioned repository at GitHub. I am rather afraid that recent releases of megacli may not compilable by historic GCC releases (e.g. in the Sailfish-SDK for SailfishOS 2.2.0 which currently still generates a working FileCase RPM file and FileCase proper).

I updated my inline-comments in filecase.pro accordingly by PR #114.

P.S.: Contributes to issue #48.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestfeature requests, suggestions, ideas etc.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions