Skip to content

Missing definition for some utf16 functions #14

@DongKat

Description

@DongKat

Hi,
I'm experimenting with building fsxfsmount on Windows. After generating the visual studio solution, I encounter this compile error:
Image
I find this issue stems from missing defintions for libfsxfs_file_entry_get_utf16_symbolic_link_target_size and libfsxfs_file_entry_get_utf16_symbolic_link_target.

Why do I need definitions for these functions?

  • I tried building with the UNICODE flags disabled; however, this consistently results in this error: "Unable to run dokan main: unable to assign drive letter\n"
  • After some debugging, I found that the mount point argument is being passed as UTF-8, while the Dokan logic expects UTF-16.

Solution

I tested a similar pattern from the UTF-8 variant—libfsxfs_file_entry_get_utf18_symbolic_link_target_size—and had some success. I can open a PR with the proposed changes later.
Please let me know if there are any specific tests that I can run before submitting the PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions