Re: How can i prevent blueprint-compiler from generating pycache files thus causing build_fs_violation
- Reply: Nuno Teixeira : "Re: How can i prevent blueprint-compiler from generating pycache files thus causing build_fs_violation"
- In reply to: Yusuf Yaman : "How can i prevent blueprint-compiler from generating pycache files thus causing build_fs_violation"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 03 Feb 2025 20:38:13 UTC
# grep blueprint-compiler work/flare-f412701ad8eb30d8ff0aa15db5cbc4997b21b340/data/resources/meson.build command: [find_program('blueprint-compiler', version: '>= 0.12.0'), 'batch-compile', '@OUTPUT@', '@CURRENT_SOURCE_DIR@', '@INPUT@'], I guess that meson.build file is running blueprint-compiler and then i assume it generates __pycache__ files and i can't even seem to delete these __pycache__ directories in the Makefile either. I saw that some ports use that environment variable to prevent generating __pycache__ files but why it doesn't work for my port while it does for others? is it an issue with blueprint-compiler program? On 2/1/25 20:12, Yusuf Yaman wrote: > Hello, > > I am trying to port a third-party Signal messaging app which has buil > dependency on devel/blueprint-compiler and the port builds fine but i am > getting build_fs_violation error in poudriere testport even though I > have that PYTHONDONTWRITEBYTECODE=1 set in MAKE_ENV variable in > Makefile. How can i overcome this? Thanks in advance. > > =>> Checking for filesystem violations... done > =>> Error: Filesystem touched during build: > extra: > usr/local/lib/python3.11/site-packages/blueprintcompiler/outputs/xml/__pycache__ > extra: > usr/local/lib/python3.11/site-packages/blueprintcompiler/outputs/__pycache__ > extra: usr/local/lib/python3.11/site-packages/blueprintcompiler/__pycache__ > extra: > usr/local/lib/python3.11/site-packages/blueprintcompiler/language/__pycache__ > =>> Cleaning up wrkdir > > https://github.com/nxjosephofficial/flare-ports > > Best regards, > > Yusuf. >