Hi,
I just checked the IM repository and those *.o/*.so/*.a files are not
there. You can check here:
https://sourceforge.net/p/imtoolkit/im/HEAD/tree/trunk/
The FFTW dll/exe files, on the other hand, are there because they are not
generated by us.
Best,
Scuri
2018-01-20 16:12 GMT-02:00 sur-behoffski <sur_behoff...@grouse.com.au>:
> G'day,
>
> Yeah, I know I was going to be quiet... but the very first item on
> my "weirdness list" came up with a surprise result.
>
> There are quite a number of compiler/linker output files committed to
> the Subversion repository "imtoolkit-im" (the basis of the "IM"
> project), e.g.:
>
> $ find . -type f -iname "*.o"
> ./imtoolkit-im/trunk/im/obj/im_process_omp/Linux414_64/im_render.o
> ./imtoolkit-im/trunk/im/obj/im_process_omp/Linux414_64/im_co
> nvertbitmap.o
> ./imtoolkit-im/trunk/im/obj/im_process_omp/Linux414_64/im_color.o
> ./imtoolkit-im/trunk/im/obj/im_process_omp/Linux414_64/im_logic.o
> ./imtoolkit-im/trunk/im/obj/im_process_omp/Linux414_64/im_ge
> ometric.o
> ./imtoolkit-im/trunk/im/obj/im_process_omp/Linux414_64/im_hi
> stogram.o
> [...]
> ./imtoolkit-im/trunk/im/obj/im_jp2/Linux414_64/jas_cm.o
> ./imtoolkit-im/trunk/im/obj/im_jp2/Linux414_64/jpc_mqenc.o
> ./imtoolkit-im/trunk/im/obj/im_jp2/Linux414_64/jpc_tagtree.o
> ./imtoolkit-im/trunk/im/obj/im_jp2/Linux414_64/jas_tvp.o
> ./imtoolkit-im/trunk/im/obj/im_jp2/Linux414_64/jp2_cod.o
> ./imtoolkit-im/trunk/im/obj/im_process/Linux414_64/im_render.o
> ./imtoolkit-im/trunk/im/obj/im_process/Linux414_64/im_conver
> tbitmap.o
> ./imtoolkit-im/trunk/im/obj/im_process/Linux414_64/im_color.o
> ./imtoolkit-im/trunk/im/obj/im_process/Linux414_64/im_logic.o
> $ find . -type f -iname "*.a"
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_fftw.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_jp2.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_process.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_process_omp.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_lzo.a
> $ find . -type f -iname "*.so"
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_process_omp.so
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_lzo.so
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_fftw.so
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim.so
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_process.so
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_jp2.so
> $ find . -type f -iname "*.a"
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_fftw.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_jp2.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_process.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_process_omp.a
> ./imtoolkit-im/trunk/im/lib/Linux414_64/libim_lzo.a
> $ find . -type f -iname "*.obj"
> $ find . -type f -iname "*.dll"
> ./imtoolkit-im/trunk/fftw3/lib/Win64/libfftw3l-3.dll
> ./imtoolkit-im/trunk/fftw3/lib/Win64/libfftw3-3.dll
> ./imtoolkit-im/trunk/fftw3/lib/Win64/libfftw3f-3.dll
> ./imtoolkit-im/trunk/fftw3/lib/Win32/libfftw3l-3.dll
> ./imtoolkit-im/trunk/fftw3/lib/Win32/libfftw3-3.dll
> ./imtoolkit-im/trunk/fftw3/lib/Win32/libfftw3f-3.dll
> $ find . -type f -iname "*.exe"
> ./imtoolkit-im/trunk/fftw3/bin/Win64/bench.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win64/fftw-wisdom.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win64/fftwl-wisdom.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win64/benchf.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win64/benchl.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win64/fftwf-wisdom.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win32/bench.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win32/fftw-wisdom.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win32/fftwl-wisdom.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win32/benchf.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win32/benchl.exe
> ./imtoolkit-im/trunk/fftw3/bin/Win32/fftwf-wisdom.exe
>
> The kernel version number -- 4.14 in the repository sometime matches,
> sometimes differs, depending on the machine I'm working on. Where a
> match occurs, the compilation mostly turns into a no-op, except for
> final linking and library production stages.
>
> There appears to be no intermediate files in the canvasdraw-cd (CD) or
> iup-iup (IUP) Subversion project repositories, so the IM case is
> unusual.
>
> Furthermore, a look at the IM-3.12_Sources.tar.gz release tarball shows
> that no intermediate files are included there, including no DLLs or
> EXEs.
>
> ----
>
> My belief is that intermediate files, generated by the toolchain,
> should be deleted from the imtoolkit-im Subversion repository (unless
> a file is a binary blob, e.g. a driver, from a third-party; perhaps
> give these a .bin extension). However, this is not urgent, as long as
> people understand the current situation; in particular, it does not
> need to be scheduled before any IUP release.
>
> cheers,
>
> s-b etc
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Iup-users mailing list
> Iup-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/iup-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iup-users
