mirror of
https://github.com/RGBCube/serenity
synced 2025-05-14 05:14:59 +00:00
3d6b838df3
The implemented cloning mechanism should be sound: - If a PartitionTable is passed a File with ShouldCloseFileDescriptor::Yes, then it will keep it alive until the PartitionTable is destroyed. - If a PartitionTable is passed a File with ShouldCloseFileDescriptor::No, then the caller has to ensure that the file descriptor remains alive. If the caller is EBRPartitionTable, the same consideration holds. If the caller is PartitionEditor::PartitionModel, this is satisfied by keeping an OwnPtr<Core::File> around which is the originally opened file. Therefore, we never leak any fds, and never access a Core::File or fd after destroying it.
11 lines
264 B
CMake
11 lines
264 B
CMake
set(SOURCES
|
|
DiskPartitionMetadata.cpp
|
|
EBRPartitionTable.cpp
|
|
GUIDPartitionTable.cpp
|
|
MBRPartitionTable.cpp
|
|
PartitionableDevice.cpp
|
|
PartitionTable.cpp
|
|
)
|
|
|
|
serenity_lib(LibPartition partition)
|
|
target_link_libraries(LibPartition PRIVATE LibCore)
|